next.js
71de7e6a - test: migrate and explain root-inference deploy exclusions (#99012)

Commit
26 days ago
test: migrate and explain root-inference deploy exclusions (#99012) ## Summary Base this PR directly on #98430 and migrate the six workspace-root inference suites from `skipDeployment` to `@force-gate !deploy`, including removal of their `skipped` early returns. This PR now contains its own conversions and no longer depends on the migration in #98156. Retain the deployment exclusions with concrete explanations: Vercel’s builder supplies `NEXT_PRIVATE_OUTPUT_TRACE_ROOT`, bypassing automatic workspace-root inference. Diagnostic assertions would not exercise that path, while successful imports and absent warnings would not establish that workspace detection worked. The home-directory boundary tests also change `HOME` for a locally managed Next.js process. ## Verification - Formatting and ESLint passed for all six files. - All 24 gate pragma-transform unit tests passed, including `describe.each` support. - Verified all six force-gates attach successfully and test logic matches #98430 after removing only the legacy deployment skip machinery. Final file contents match the previously reviewed PR head. - Deployment-mode collection and gate-runtime tests were blocked by missing `node-fetch` in the local installation; no deployments ran. - Bootstrap and watch builds were attempted but stalled without output and were stopped. <!-- NEXT_JS_LLM -->
Author
Parents
Loading