test: enable deployment fixtures with Corepack and portable tarballs (#99192)
## Summary Enable deployment coverage for seven fixture suites while preserving dependency declarations, test bodies, assertions, and unrelated mode restrictions. - Set `ENABLE_EXPERIMENTAL_COREPACK: '1'` for `geist-font`, `gssp-redirect`, `rewrite-with-browser-history`, `router-hash-navigation`, and `scroll-back-restoration` so Vercel installs with the pnpm version declared by the generated `packageManager` field. These fixtures do not require committed pnpm lockfiles or `npm_config_frozen_lockfile` overrides. - Use fixture-relative tarball dependencies for `self-importing-package` and `typeof-window` so deployment installation does not refer to paths on the GitHub Actions runner. - Apply the Corepack setting to both suites using the shared source-map fixture. Retain their deployment exclusions because their assertions require runtime logs or a local Node.js inspector; they are not counted as deployment passes. ## Verification Ran focused `pnpm test-deploy-turbo --runTestsByPath` tests with `VERCEL_TURBOPACK_TEST_TEAM=vtest314-next-e2e-tests`, `NEXT_E2E_TEST_TIMEOUT=240000`, and `NEXT_TEST_VERSION=canary` (resolved to `16.4.0-canary.53`): - All five affected deploy-enabled suites passed in normal mode: **26/26 tests**. - With `__NEXT_CACHE_COMPONENTS=true` and `__NEXT_EXPERIMENTAL_CACHED_NAVIGATIONS=true`, the same five suites passed: **26/26 tests**. Remote build logs confirmed both features were enabled. - All ten deployments detected the Corepack flag and `pnpm@10.33.0`, installed successfully without source lockfiles, and executed the browser/HTTP assertions. - The unchanged `self-importing-package` and `typeof-window` tarball fixtures passed in both modes in the preceding validation (two tests per mode); this update does not touch them. - Prettier, ESLint, and `git diff --check` passed. The Next.js watch build completed with zero type errors. The full pre-push build completed 17/18 tasks; native SWC remains blocked because Cargo is unavailable locally. These focused runs validate the fixture changes against published canary, not all CI checks on the updated PR head. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment