-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fix HMR when module evaluation throws #4151
Merged
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
update snapshots
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
sokra
added
the
pr: automerge
Kodiak will merge these automatically after checks pass
label
Mar 10, 2023
|
alexkirsz
suggested changes
Mar 10, 2023
sokra
removed
the
pr: automerge
Kodiak will merge these automatically after checks pass
label
Mar 10, 2023
alexkirsz
approved these changes
Mar 10, 2023
Benchmark for 2583041
Click to view full benchmark
|
sokra
added
the
pr: automerge
Kodiak will merge these automatically after checks pass
label
Mar 10, 2023
Benchmark for 50dee6fClick to view benchmark
|
timneutkens
pushed a commit
to vercel/next.js
that referenced
this pull request
Mar 10, 2023
# Bugfixes * vercel/turborepo#4149 * vercel/turborepo#4151 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
### Description * before a self accepting module was disconnected from it's parents and after an error in module evaluation it failed to continue updating. * now it keep being connected to its parents, allowing a HMR update to bubble to the parent when evaluation lead to an error ### Testing Instructions Introduce a syntax/parse error and fix it again Co-authored-by: Alex Kirszenberg <[email protected]>
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
### Description * before a self accepting module was disconnected from it's parents and after an error in module evaluation it failed to continue updating. * now it keep being connected to its parents, allowing a HMR update to bubble to the parent when evaluation lead to an error ### Testing Instructions Introduce a syntax/parse error and fix it again Co-authored-by: Alex Kirszenberg <[email protected]>
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
### Description * before a self accepting module was disconnected from it's parents and after an error in module evaluation it failed to continue updating. * now it keep being connected to its parents, allowing a HMR update to bubble to the parent when evaluation lead to an error ### Testing Instructions Introduce a syntax/parse error and fix it again Co-authored-by: Alex Kirszenberg <[email protected]>
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.
Description
Testing Instructions
Introduce a syntax/parse error and fix it again
Co-authored-by: Alex Kirszenberg [email protected]