Make it possible to read Next.js script tags containing RSC payload data from the chrome extension #1144
+170
−56
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
…ata from the chrome extension The Next.js server will add a bunch of script tags to the body containing RSC payload data. The @rsc-parser/embedded package can already read this by making a pretend request. With this change, @rsc-parser/chrome-extension can read it too.
alvarlagerlof
deleted the
let-the-chrome-extension-read-next-js-script-tag-data
branch
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.
The Next.js server will add a bunch of script tags to the body containing RSC payload data.
The @rsc-parser/embedded package can already read this by making a pretend request. With this change, @rsc-parser/chrome-extension can read it too.
Screen.Recording.2024-07-13.at.01.47.02.mov