chore(deps): update dependency vite-tsconfig-paths to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite-tsconfig-paths	^3.5.0 -> ^4.0.0

---

Release Notes

aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)

v4.3.1

Compare Source

v4.3.0

Compare Source

v4.2.3

Compare Source

• 4cc78b4 fix: avoid breaking change from #​128

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

• 7a97869 If a tsconfig file is malformed and cannot be parsed (e.g. its extends property points to a non-existent file), an error is now logged instead of crashing the process. You can disable parsing error logs by setting ignoreConfigErrors: true in the plugin options.

v4.1.0

Compare Source

• 9766de8 If the projects option is used, any missing tsconfig files will be silently ignored (other than a debug log, enabled with DEBUG="vite-tsconfig-paths" environment variable).

v4.0.9

Compare Source

v4.0.8

Compare Source

v4.0.7

Compare Source

v4.0.6

Compare Source

v4.0.5

Compare Source

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

• Stop using the tsconfig-paths package
  It is better to let Vite handle all of the resolving, so that this plugin can be only responsible for the path mapping.

  At the same time, I am also adding the tsconfck package, which handles the loading of tsconfig.json files for us. This package is also used in Vite core (we should have Vite expose it in the future, to avoid the duplication).

  The tsconfig-paths package was previously responsible for config loading and much of the path resolving logic, but now we can ditch it! I'm also ditching the recrawl-sync package, which was used for crawling the filesystem in search of tsconfig.json files.

• Remove the extensions option
  Since the file resolution is delegated to Vite core, this option is no longer necessary.

• Add the parseNative option
  The tsconfck package has a parseNative function that's able to delegate config loading to the TypeScript compiler. If you encounter a bug in tsconfig.json file loading, you can try passing parseNative: true to see if that helps. But you should avoid enabling it otherwise, since it has a noticeable performance cost (up to 600ms roughly speaking).

v3.6.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[github-advanced-security]

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud