-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency vite-tsconfig-paths to v4 #229
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/vite-tsconfig-paths-4.x
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
5ef1096
to
8d6af80
Compare
8d6af80
to
62bb99a
Compare
62bb99a
to
2ca87b0
Compare
2ca87b0
to
de656f5
Compare
de656f5
to
1c2e526
Compare
1c2e526
to
61080f2
Compare
61080f2
to
8780553
Compare
8780553
to
4c79523
Compare
4c79523
to
fece3ae
Compare
Deployment failed with the following error:
|
496a1b8
to
b3a9034
Compare
Deployment failed with the following error:
|
9d84082
to
5117251
Compare
5117251
to
055de96
Compare
055de96
to
2b40040
Compare
7bdc0a0
to
dfb4c07
Compare
e7868b8
to
501fa1c
Compare
b8e4a5a
to
99164fb
Compare
99164fb
to
89544c9
Compare
89544c9
to
c452b01
Compare
b0c4ea2
to
38fc86e
Compare
38fc86e
to
a4f70fc
Compare
bf3498b
to
132a0d7
Compare
132a0d7
to
77319aa
Compare
77319aa
to
448d4e1
Compare
448d4e1
to
22db0fb
Compare
164b07a
to
dab80c0
Compare
dab80c0
to
f49dabf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.6.0
->4.3.2
Release Notes
aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)
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).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 has been generated by Mend Renovate. View repository job log here.