vercel__next.js/test/e2e/og-api/standalone.test.ts at codex/fallback-root-cache - vercel__next.js - GetSkill.work

skills/vercel__next.js

mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Files

T

Hendrik Liebau 2ca0d5df1c [test] split og-api test suite into default and standalone variants (#93915 )

The fixture's `next.config.js` had `output: 'standalone'` hardcoded,
which is meaningless on Vercel deployments (the standalone directory is
ignored) but became a build-time crash after #93684 made the Turbopack
NFT generator skip `next-server.js.nft.json` whenever an adapter is
configured. With `output: 'standalone'` still active,
`writeStandaloneDirectory` then fails with `ENOENT` when it tries to
read that file
([x-ref](https://github.com/vercel/next.js/actions/runs/26006483168/job/76441905221)).

This PR splits the `og-api` E2E suite into a default variant and a
`standalone.test.ts` wrapper that enables `output: 'standalone'` via the
`TEST_OUTPUT_STANDALONE` env var, and excludes the standalone wrapper
from the deploy test manifest.

The default variant still runs in `deploy` mode and preserves coverage
of `next/og` from Pages Router API routes, App Router route handlers
(edge and node), and middleware — paths not covered by the metadata-*
fixtures. The standalone variant continues to exercise the trace-copy
assertion in `next start` mode.

---------

Co-authored-by: Tim Neutkens <tim@timneutkens.nl>

2026-05-18 12:14:43 +00:00

4 lines

69 B

TypeScript

Raw Permalink Blame History

	`process.env.TEST_OUTPUT_STANDALONE = 'true'`

	`require('./index.test')`