8c7f0dc960
## Why? We have a flaky test with `NODE_OPTIONS='--inspect'` test in https://github.com/vercel/next.js/blob/canary/test/integration/cli/test/index.test.js because with Turbopack, we run several integration tests concurrently. Our integration tests are ran concurrently, so anything that adds `NODE_OPTIONS='--inspect'` can clash with another when `run-tests.js` is ran. Hence, the result below. - https://github.com/vercel/next.js/actions/runs/8189378285/job/22394053022?pr=62999 You can confirm this locally by running `TURBOPACK=1 node run-tests.js --test-pattern "test\\/integration\\/(cli|config-mjs)\\/test\\/index\\.test\\.js"`. ## Changes Both https://github.com/vercel/next.js/blob/canary/test/integration/config-mjs/test/index.test.js and https://github.com/vercel/next.js/blob/canary/test/integration/config/test/index.test.js add a now unnecessary `NODE_OPTIONS='--inspect'`, so we should be good to remove them. Closes NEXT-2759 |
||
|---|---|---|
| .. | ||
| components | ||
| node_modules | ||
| pages | ||
| test | ||
| .gitignore | ||
| next.config.js | ||