feat: docs/** content hot reload
#9842
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
a-hariti
changed the title
docs/** content change hot reloaddocs/** content hot reload
stephanie-anderson
approved these changes
Apr 29, 2024
Bundle ReportChanges will increase total bundle size by 984 bytes ⬆️
|
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.
Authoring quality of life improvement
Next.js seems to be blind to content changes under
/docs/**/because content files are outside the module dependency graphThere's no obvious way in the docs to let Next.js know about the changes directly
This is workaround establishes a Web Socket connection with a backend file watcher and triggers a hot reload as needed.
This solution should add ~0 js to the bundle sizse.
Closes #9038