rsnext/bench/vercel
Steven 12c800e35c
chore: remove chalk in favor of picocolors (#55992)
Similar to PR https://github.com/vercel/next.js/pull/53115, this PR removes `chalk` in favor of `picocolors`
2023-09-27 21:00:52 +00:00
..
benchmark-app misc: fix benchmark script (#44592) 2023-01-05 13:46:41 +00:00
.env.dev misc: add benchmarking script for edge rendering (#40716) 2022-09-27 17:57:16 +02:00
.gitignore misc: add benchmarking script for edge rendering (#40716) 2022-09-27 17:57:16 +02:00
bench.js chore: remove chalk in favor of picocolors (#55992) 2023-09-27 21:00:52 +00:00
chart.js misc: fix benchmark script (#44592) 2023-01-05 13:46:41 +00:00
gen-request.js misc: fix benchmark script (#44592) 2023-01-05 13:46:41 +00:00
generate-package-json.js misc: fix benchmark script (#44592) 2023-01-05 13:46:41 +00:00
package.json fix: upgrade listr2 from 5.0.5 to 5.0.8 (#55223) 2023-09-13 21:02:14 +00:00
project-utils.js chore: remove chalk in favor of picocolors (#55992) 2023-09-27 21:00:52 +00:00
README.md misc: add benchmarking script for edge rendering (#40716) 2022-09-27 17:57:16 +02:00

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 pack the 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