Files
vercel__next.js/bench/heavy-npm-deps/package.json
Luke Sandberg 9ba29b4125 Revert "Revert "Revert "Revert "Add a --webpack flag and default --turbopack to true (#84216)"""" (#84394)
Reverts vercel/next.js#84389

Attempt number 3, #84374 fixed propagation of bundler environment variables to vercel cli operations, to ensure the test configuration is respected. 

[Deployment Tests Run 1](https://github.com/vercel/next.js/actions/runs/18146684793/job/51649631635).  A fair number of failures.

[Deployment Tests Run 2](https://github.com/vercel/next.js/actions/runs/18154875270). After #84395.  These still have a set of failures, but i confirmed that the deployment builds are running `webpack`.  

The tests that are failing are related to 'prefetches' (test/e2e/app-dir/segment-cache/prefetch-runtime/prefetch-runtime.test.ts and test/e2e/app-dir/segment-cache/prefetch-layout-sharing/prefetch-layout-sharing.test.ts) and generally the error is a timeout.  Recent deployment runs for canary releases are also failing, but on different tests.


Trying again after #[84419](https://github.com/vercel/next.js/pull/84419).  [Deployment Tests Run 3](https://github.com/vercel/next.js/actions/runs/18173375427).  Failures appeared flaky, rerunning failures...
2025-10-01 17:04:17 -07:00

24 lines
625 B
JSON

{
"name": "bench-heavy-npm-deps",
"version": "0.1.0",
"private": true,
"scripts": {
"dev-turbopack": "next dev --turbopack",
"dev-webpack": "next dev --webpack",
"build-turbopack": "next build --turbopack",
"build-webpack": "next build --webpack",
"start-turbopack": "next start",
"start-webpack": "next start",
"build-application": "next build",
"start-application": "next start"
},
"dependencies": {
"@mantine/core": "^7.10.1",
"lodash-es": "^4.17.21",
"lucide-react": "^0.383.0",
"mermaid": "^10.9.1",
"next": "workspace:*",
"tailwindcss": "3.2.7"
}
}