-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Support Vite 3.1 #4752
Support Vite 3.1 #4752
Conversation
🦋 Changeset detectedLatest commit: 60a1a59 The changes in this PR will be included in the next version bump. This PR includes changesets to release 16 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.
Why not go ahead and upgrade to 3.1 here too?
do we still want to pin it to |
Let's try |
Updated to |
Looks like the new Vite types are messing with the Astro build. I reverted the Vite version bump at the meantime and we can probably tackle the types stuff in another PR. |
* Support Vite 3.1 * Update ~3.1.0 * Revert Vite bump
Changes
While checking out #4727, I noticed that we're incorrectly accessing the
this
context in thehandleHotUpdate
hook. This was previously the Vite plugin object, but was removed with the object hooks feature: vitejs/vite#9634 and vitejs/vite#9885Testing
Tested locally. This issue can be triggered when updating an Astro file. Ideally #4454 should cover this.
Docs
N/A. internal change.