You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Previously, the segment path handling was returning before the x-nextjs-cache headers were sent, this moves it below that to ensure that the correct cache headers are added.
● ReactRefreshRequire › propagates a module that stops accepting in next version
expect(received).toEqual(expected) // deep equality
- Expected - 0
+ Received + 1
Array [
"init BarV2",
"init FooV1",
+ "init BarV2",
]
440 | // Since the export list changed, we have to re-run both the parent
441 | // and the child.
> 442 | expect(await session.evaluate(() => (window as any).log)).toEqual([
| ^
443 | 'init BarV2',
444 | 'init FooV1',
445 | ])
at Object.toEqual (development/acceptance/ReactRefreshRequire.test.ts:442:63)
Read more about building and testing Next.js in contributing.md.
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.
Previously, the segment path handling was returning before the
x-nextjs-cache
headers were sent, this moves it below that to ensure that the correct cache headers are added.