PACK-5183 #150
PACK-5183 #150
Conversation
# Add automated benchmark runner for module-cost ## What? This PR adds an automated benchmark runner for the module-cost benchmark, allowing for consistent measurement of module loading and execution times. ## Why? It is to tedious and error prone to run the benchmark. ## Usage Build `next` and turbopack however you like ``` pnpm i pnpm prepare-bench pnpm build-webpack (or build-turbopack) pnpm benchmark ``` ## How? v0 mostly
|
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard. ⏱️ Latest scan covered changes up to commit cb1753b (latest) |
austinderek
force-pushed
the
canary
branch
2 times, most recently
from
9e9ee85 to
4e06942
Compare
|
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard. ⏱️ Latest scan covered changes up to commit f7b798a (latest) |
austinderek
force-pushed
the
canary
branch
2 times, most recently
from
9e9ee85 to
4e06942
Compare
|
✅ This pull request was succesfully scanned and it was determined that it does not contain any changes that present immediate security concerns. If you would still like for it to be reviewed by an expert from our reviewer community, you can submit it manually via the HackerOne PullRequest dashboard. ⏱️ Latest scan covered changes up to commit 5cdb3b2 (latest) |
austinderek
force-pushed
the
canary
branch
2 times, most recently
from
d633789 to
4e06942
Compare
🔄 This is a mirror of upstream PR #82359