[next] Populate middlewareRawSrc using middleware originalSource #9602
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
cb1kenobi
requested review from
TooTallNate,
EndangeredMassa,
styfle,
Ethan-Arrowood and
ijjk
as code owners
styfle
approved these changes
Mar 3, 2023
ijjk
reviewed
Mar 4, 2023
ijjk
approved these changes
Mar 4, 2023
|
Canary with above mentioned Next.js change is now available in |
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.
Next.js will pass the original middleware matching routes through to the middleware manifest once vercel/next.js#46753 lands. This PR will take those original values and put them in the middleware route
middlewareRawSrcproperty.NOTE: The tests will need to be updated once the Next.js version is updated in the fixtures.