Repository navigation
docs: enable the testing API at build and server startup - #101443
Merged
Merged
Conversation
Contributor
Tests PassedCommit: 86c64dd |
aurorascharff
marked this pull request as ready for review
November 9, 2026 10:10
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.
Summary
Production tests need the Instant Navigation testing API enabled during both the build and server startup. With the flag set only during the build, initial page loads render request-time content during
instant()tests while client navigations still pause.The command examples now set the flag for both stages. The skill templates link to the config reference instead of repeating its explanation, while retaining their environment and server lifecycle instructions. The static-shell eval also passes the flag to its Playwright server.
Addresses agent feedback finding 5264.
Updated files
docs/01-app/03-api-reference/05-config/01-next-config-js/exposeTestingApiInProductionBuild.mdxdocs/01-app/02-guides/instant-navigation.mdxskills/next-cache-components-optimizer/rig-template.mdskills/next-partial-prefetching-adoption/rig-template.mdskills/next-partial-prefetching-optimizer/rig-template.mdevals/evals/agent-050-optimize-static-shell/playwright.config.tsevals/evals/agent-050-optimize-static-shell/instant-nav.rig.mdVerification
@next/playwrightversions 16.4.2 and 16.5.0-canary.45. Restarting the same build with the variable enabled fixed initial page locking on both versions.Full repository lint previously failed on unused Rust task items in untouched files. Process cleanup also reported a sandbox permission error. The full agent-eval suite was not run.