0cb1c40400
Since we reset the test project on every e2e CI run, deployment protection is automatically enabled by default. This adds an option to the reset project workflow to disable deployment protection. Our test runners need to be able to hit these pages from an unauthenticated browser in order for the tests to work. Verified tests are running properly in [this run](https://github.com/vercel/next.js/actions/runs/6971348806/job/18971225559) (fixing any failing tests themselves are out of scope for this PR; will evaluate once the run finishes) Closes NEXT-1732 |
||
|---|---|---|
| .. | ||
| benchmark-app | ||
| .env.dev | ||
| .gitignore | ||
| bench.js | ||
| chart.js | ||
| gen-request.js | ||
| generate-package-json.js | ||
| package.json | ||
| project-utils.js | ||
| README.md | ||
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