Bump vite-tsconfig-paths from 3.5.1 to 4.3.1

[dependabot]

Bumps vite-tsconfig-paths from 3.5.1 to 4.3.1.

Release notes

Sourced from vite-tsconfig-paths's releases.

v4.3.0

• 353926a feat: use jsconfig.json if present (closes #22)

v4.2.3

• 4cc78b4816eb7eea13cae878d8a4b6da8d691c27 fix: avoid breaking change from #128

v4.2.2

• d496ea9c90c2e1159c53fc54d5e435d4316d47ee fix: forward options when calling this.resolve (#128) (thanks to @​pcattori)

⚠️ This release may have broken Vite versions older than 5.0

v4.2.1

• 8b4f6c8872bce9de5480fb7104418e77ee6fe889 feat(perf): leverage tsconfk caching to skip redundant work (#119) (thanks to @​fwouts)

v4.2.0

• 7a97869db40bf42924856bf586b615cb3003dbc7 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

• 9766de8a0dc0889800005c5c6b3f8c3954171d08 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.0

• 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).

Commits

• ca4e2aa 4.3.1
• cb9b582 fix: lazily import tsconfck
• afe1fed 4.3.0
• c8c3e10 chore: update lockfile
• 353926a feat: use jsconfig.json if present
• dd3fc7e 4.2.3
• 4cc78b4 fix: avoid breaking change from #128
• fcea268 nit: use baseUrl variable
• ae57cbd 4.2.2
• d496ea9 fix: forward options when calling this.resolve (#128)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[dependabot]

Superseded by #51.