fix: pin vite to 8.0.16 to fix broken production build#110
Merged
Conversation
…n in 8.1.3 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
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
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.
PR #109 (dependency updates) bumped vite from 8.0.16 to 8.1.3, which is currently main's latest release. That bump broke the production build: rolldown fails to resolve
@frontend/composables/useAuthSocketfrom App.vue withRolldown failed to resolve import, even thoughvue-tsc/tscresolve the same import fine (confirming this is a bundler-specific regression, not a real broken import).Verified by bisecting: pinning vite back to exactly 8.0.16 (with vite-plugin-vue-devtools and vue left at their bumped versions) fixes the build, reproduced with a fully cleared vite/dist cache. Checked npm — 8.1.3 is vite's current latest, no newer patch exists yet to pick up a fix.
Pinned vite to an exact version (no caret) rather than a range, since a caret range would let a future
bun installsilently re-resolve to another broken 8.x release.— Claude Sonnet 5