-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Upgrade to Vite 4 #7543
Upgrade to Vite 4 #7543
Conversation
🦋 Changeset detectedLatest commit: 8c12306 The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this broke paths.assets
handling. investigating
I'm probably stupid, but I went into package.json and set
And then |
I haven't seen that. Can you share a project that reproduces the issue? |
Just tried to recreate the issue in StackBlitz but it seems to work fine, so guessing it's something specific to this (private) repo. I tried renaming
I don't really know where to even start debugging the issue since I don't know a lot about NPM's inner workings. I could use |
That sounds like you still have Vite 3 in a Another thing you could try is |
That fixed it. Really appreciate the help - realise you're not tech support! Not sure what was wrong with my setup 😅 |
Shouldn't affect SvelteKit or its users much other than bumping a version. One nice change is that it fixes the value of
NODE_ENV
to be more inline with what one would expect, which I think should help us clean some stuff upTo migrate, simply bump your Vite and SvelteKit versions to the latest versions. See the full Vite 4 migration guide and announcement for more details