docs: codify generated entry refactor guidance#640
Merged
southpolesteve merged 1 commit intomainfrom Mar 22, 2026
Merged
Conversation
commit: |
|
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
1 participant
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.
Summary
Add repo guidance for the refactor pattern we've been using to make generated entry code more maintainable:
vpfor local check/test/build loopspackages/vinext/src/entries/*as thin codegen gluepackages/vinext/src/server/*/bigbonkreview loop for high-risk refactorsWhy
We've been steadily extracting App Router runtime logic out of large generated template strings. This codifies the broad strokes of that pattern in
AGENTS.mdso future agents keep moving in the same direction instead of reintroducing large inline runtime subsystems.Testing
vp check AGENTS.md