This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
fix(vite): handle all vite middleware routes #8601
Merged
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
|
|
✅ Deploy Preview for nuxt3-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
antfu
added
the
🔨 p3-minor-bug
danielroe
approved these changes
Nov 1, 2022
pi0
changed the title
pi0
approved these changes
Nov 2, 2022
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
🔗 Linked issue
Fix nuxt/nuxt#15286
❓ Type of change
📚 Description
Vite plugin might register their custom server middleware to the Vite dev server, for example:
#7989 introduced a regression that bypassed all custom vite middleware. This PR fixes it by checking the registered routes to Vite middleware and forwarding them as-is. This also removes the hard-code
/__nuxt_vite_node__handling.📝 Checklist