33db463fe4
### What? Upgrade jest to its latest version ### Why? #56899 fails because historically Jest stripped the globals in Node.js, but 28+ isn't doing that anymore. If we upgrade, we don't have to keep track of Node.js globals and when they are added. This will be useful in removing even more polyfills for things that are natively shipped in Node.js now. ### How? Jest 29 introduced a change to the snapshot format: https://jestjs.io/blog/2022/08/25/jest-29 First, I tried setting the old compat option to not require updating snapshots, but some tests were still failing: https://dev.azure.com/nextjs/next.js/_build/results?buildId=70633&view=logs&j=8af7cf9c-43a1-584d-6f5c-57bad8880974&t=7ae70e63-3625-50f4-6764-5b3e72b4bd7a&l=273 So going through the pain now instead.
30 lines
882 B
JSON
30 lines
882 B
JSON
{
|
|
"compilerOptions": {
|
|
"strict": false,
|
|
"noEmit": true,
|
|
"allowJs": true,
|
|
"resolveJsonModule": true,
|
|
"jsx": "react",
|
|
"module": "esnext",
|
|
"target": "ESNext",
|
|
"esModuleInterop": true,
|
|
"moduleResolution": "node",
|
|
"baseUrl": ".",
|
|
"types": ["react", "jest", "node", "trusted-types", "jest-extended"],
|
|
"paths": {
|
|
"development-sandbox": ["test/lib/development-sandbox"],
|
|
"next-test-utils": ["test/lib/next-test-utils"],
|
|
"amp-test-utils": ["test/lib/amp-test-utils"],
|
|
"next-webdriver": ["test/lib/next-webdriver"],
|
|
"e2e-utils": ["test/lib/e2e-utils"]
|
|
}
|
|
},
|
|
"include": [
|
|
"test/**/*.test.ts",
|
|
"test/**/*.test.tsx",
|
|
"test/**/test/*",
|
|
"packages/next/types/compiled.d.ts",
|
|
"test/e2e/pages-dir/client-navigation/index.test.js",
|
|
"test/e2e/pages-dir/client-navigation/rendering.js"
|
|
]
|
|
}
|