Remove the Cache Components deployment-test alias (#99446)
## Summary Remove `NEXT_PRIVATE_EXPERIMENTAL_CACHE_COMPONENTS` to simplify how deployment tests enable Cache Components. Capture `__NEXT_CACHE_COMPONENTS` in the generated test config instead, preserving deployment coverage and explicit config overrides without a separate environment-variable alias. ## Verification - `pnpm test-unit test/unit/next-deploy-failure/next-deploy-failure.test.ts --runTestsByPath --runInBand` — 19 tests passed. - Loaded nine generated configs in fresh processes: enabled, disabled, and unset test flags crossed with enabled, disabled, and unset `cacheComponents` config. Flag propagation and explicit config overrides were preserved. - Live Vercel deployment tests passed against the preview package for `654cad9519ce5af015d3cdbe23dd8ed1538662b8`, using Turbopack and `__NEXT_CACHE_COMPONENTS=true`: `not-found-non-document-dynamic` (4 tests, inherited flag) and `prefetch-inlining-no-cache-components` (3 tests, explicit opt-out). The inherited-flag build enabled Cache Components and produced partial prerenders. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment