Open
Conversation
The override was needed when vite 8 was in beta because vitest's peerDependencies did not allow pre-release versions. With vite 8 now GA and vitest 4.1.4 declaring `vite: ^6.0.0 || ^7.0.0 || ^8.0.0`, npm resolves vite 8.0.9 from devDependencies without the override.
natsukium
force-pushed
the
chore/remove-vite-override
branch
from
7c2f24f to
d656f71
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
overrides.viteentry was added when vite 8 was in beta because vitest's peerDependencies did not allow pre-release versions.@vitest/mocker) declarevite: '^6.0.0 || ^7.0.0 || ^8.0.0', so npm resolves vite 8.0.9 from devDependencies without the override.package-lock.json.Test plan
npm installresolves vite 8.0.9 (verified vianpm ls vite)npm run check(typecheck / lint / format / test, 77 tests)npm run build(vite v8.0.9)