mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Sebastian "Sebbie" Silbermann
d470d18941
The weekly `test-e2e-project-reset-cron` workflow never defined `VERCEL_TURBOPACK_TEST_TEAM` or `VERCEL_TURBOPACK_TEST_TOKEN`, even though `run-e2e-test-project-reset.mjs` iterates over all three deploy test teams. Because `resetProject` defaulted `teamId` and `token` to the base team, and a destructuring default fires on an explicit `undefined`, the turbopack iteration silently resolved to `vtest314-next-e2e-tests`. The cron has therefore been deleting and recreating the base team's project twice per run while never resetting the turbopack team's project, and reporting success throughout. This dates back to #89458, which wired the env pair into `build_reusable.yml` and `test_e2e_deploy_release.yml` but missed the cron. This drops the defaults in favor of explicitly passing the team.
Benchmarking Next.js on production
This script allows you to measure some performance metrics of your local build of Next.js on production by uploading your current build to Vercel with an example app and running some basic benchmarks on it.
Requirements
- the Vercel CLI
Setup
Rename the provided ./env.local file to ./env and fill in the required VERCEL_TEST_TOKEN and VERCEL_TEST_TEAM values. You can find and generate those from vercel.com.
Run pnpm install, pnpm bench and profit.
Note: if you made some changes to Next.js, make sure you compiled them by running at the root of the monorepo either pnpm dev or pnpm build --force.
How it works
- with the Vercel CLI, we setup a project
- we
npm packthe local Next build and add it to the repo - we upload the repo to Vercel and let it build
- once it builds, we get the deployment url and run some tests