chore(deps): update dependency vite-tsconfig-paths to v5 #268
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.5.0
->5.1.2
Release Notes
aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)
v5.1.2
Compare Source
v5.1.1
Compare Source
${configDir}
syntax in include/exclude (#156)v5.1.0
Compare Source
skip
option for adding additional directories to be skipped when searching for tsconfig.json files (#146)importer
path before callingthis.resolve
in theirresolveId
hooks (#157)4124b09
)v5.0.1
Compare Source
v5.0.0
Compare Source
This package is now ESM only in order to align with Vite: https://vitejs.dev/guide/migration#deprecate-cjs-node-api
If your project is using CommonJS, you can rename your Vite config to use the
.mjs
or.mts
extension (depending on whether you use TypeScript or not). If you're not using Vite v5.0.0+, you may want to pin your dependency to v4 of this plugin.v4.3.2
Compare Source
v4.3.1
Compare Source
v4.3.0
Compare Source
v4.2.3
Compare Source
4cc78b4
fix: avoid breaking change from #128v4.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. itsextends
property points to a non-existent file), an error is now logged instead of crashing the process. You can disable parsing error logs by settingignoreConfigErrors: true
in the plugin options.v4.1.0
Compare Source
9766de8
If theprojects
option is used, any missing tsconfig files will be silently ignored (other than a debug log, enabled withDEBUG="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
packageIt 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 therecrawl-sync
package, which was used for crawling the filesystem in search of tsconfig.json files.Remove the
extensions
optionSince the file resolution is delegated to Vite core, this option is no longer necessary.
Add the
parseNative
optionThe
tsconfck
package has aparseNative
function that's able to delegate config loading to the TypeScript compiler. If you encounter a bug intsconfig.json
file loading, you can try passingparseNative: 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
v3.5.2
Compare Source
v3.5.1
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.
This PR was generated by Mend Renovate. View the repository job log.