cloudflare__vinext

mirror of https://github.com/cloudflare/vinext.git synced 2026-09-14 19:04:59 +08:00

Files

T

James Anderson 3f4e594e1c fix(deploy-suite): create .next/trace before build to avoid ENOENT noise on build failure (#1200 )

The Next.js deploy test harness (test/lib/next-modes/base.ts) calls
lstat('.next/trace') during destroy() and throws ENOENT if the file
doesn't exist. vinext doesn't produce a .next/trace (it's a Next.js
telemetry file), so the deploy script creates an empty one as a stub.

That stub was created AFTER 'vinext build' (line ~520), so any run where
the build (or any earlier step like 'pnpm install' / 'vinext init')
failed left .next/trace missing. The test harness then logged ENOENT for
every failed test — 303 lines per deploy-suite workflow run.

Move the stub creation to immediately after the cleanup trap is
installed, before any step that can fail. The cleanup trap runs on EXIT,
so debug artifacts are still preserved; this just ensures .next/trace is
present for the test harness regardless of whether the build succeeded.

Note: VITE_GIT_HOOKS=0 used because vp check --fix errors out when no
JS/TS files are staged (only a .sh file is changed here).

2026-05-14 13:31:08 +00:00

autopilot.sh

Initial public release of vinext

2026-02-24 09:29:39 -06:00

coverage-summary.mjs

test: add coverage summaries for integration tests in ci (#1024 )

2026-05-02 21:17:27 +00:00

e2e-cleanup.sh

ci: add Next.js deploy suite harness (#1189 )

2026-05-14 13:01:01 +00:00

e2e-deploy.sh

fix(deploy-suite): create .next/trace before build to avoid ENOENT noise on build failure (#1200 )