[turbopack] Add --no-hmr flag to next dev#95436
Draft
sampoder wants to merge 1 commit into
Draft
Conversation
Contributor
Stats cancelledCommit: 8eecf31 |
Contributor
Failing test suitesCommit: 8eecf31 | About building and testing Next.js
Expand output● instant validation › dev - client navigation › invalid - static prefetch - missing suspense around search params |
--no-hmr flag to next dev
This file contains hidden or 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
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.
This is a prototype of the idea from the work ideas list:
Essentially, with the flag
--no-hmryou have to reload the web page to see your updates. The idea being that this would give an agent certainty that they have the most up to date copy.There might be a better way of stopping these hallucinations? Hopefully, having this though gives us something we can test with.
I'm keeping the websocket open and sending messages but we're just ignoring them on the client if they would change the page (eg.
SERVER_COMPONENT_CHANGES)