Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(turbopack): Fix EcmascriptModuleFacadeModule::ident() #71338

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from

Conversation

kdy1
Copy link
Member

@kdy1 kdy1 commented Oct 16, 2024

What?

Fix ident implementation of EcmascriptModuleFacadeModule. Previous code replaces original module part, while the new implementation adds part information as a modifier.

Why?

Currently, ident implementations are not correctly aligned. This makes some modules returned from references() disappear from the final bundle.

How?

@ijjk ijjk added the created-by: Turbopack team PRs by the Turbopack team. label Oct 16, 2024
Copy link
Member Author

kdy1 commented Oct 16, 2024

@ijjk
Copy link
Member

ijjk commented Oct 16, 2024

Stats from current PR

Default Build (Increase detected ⚠️)
General
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
buildDuration 18s 16.4s N/A
buildDurationCached 15.5s 13.3s N/A
nodeModulesSize 373 MB 373 MB
nextStartRea..uration (ms) 432ms 435ms N/A
Client Bundles (main, webpack)
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
3705-HASH.js gzip 5.27 kB 5.26 kB N/A
6554.HASH.js gzip 168 B 168 B
7758-HASH.js gzip 44.5 kB 44.5 kB N/A
d2b96154-HASH.js gzip 52.6 kB 52.6 kB N/A
framework-HASH.js gzip 57.4 kB 57.4 kB N/A
main-app-HASH.js gzip 234 B 234 B
main-HASH.js gzip 32.8 kB 32.8 kB N/A
webpack-HASH.js gzip 1.71 kB 1.71 kB N/A
Overall change 402 B 402 B
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
polyfills-HASH.js gzip 39.4 kB 39.4 kB
Overall change 39.4 kB 39.4 kB
Client Pages
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
_app-HASH.js gzip 193 B 192 B N/A
_error-HASH.js gzip 192 B 192 B
amp-HASH.js gzip 510 B 510 B
css-HASH.js gzip 340 B 342 B N/A
dynamic-HASH.js gzip 1.84 kB 1.84 kB
edge-ssr-HASH.js gzip 266 B 265 B N/A
head-HASH.js gzip 363 B 363 B
hooks-HASH.js gzip 390 B 390 B
image-HASH.js gzip 4.41 kB 4.41 kB
index-HASH.js gzip 268 B 268 B
link-HASH.js gzip 2.78 kB 2.78 kB N/A
routerDirect..HASH.js gzip 326 B 328 B N/A
script-HASH.js gzip 396 B 395 B N/A
withRouter-HASH.js gzip 322 B 324 B N/A
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 8.08 kB 8.08 kB
Client Build Manifests
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
_buildManifest.js gzip 751 B 746 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
index.html gzip 525 B 523 B N/A
link.html gzip 538 B 537 B N/A
withRouter.html gzip 520 B 519 B N/A
Overall change 0 B 0 B
Edge SSR bundle Size
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
edge-ssr.js gzip 128 kB 128 kB N/A
page.js gzip 187 kB 187 kB N/A
Overall change 0 B 0 B
Middleware size
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
middleware-b..fest.js gzip 669 B 666 B N/A
middleware-r..fest.js gzip 156 B 156 B
middleware.js gzip 31 kB 31 kB N/A
edge-runtime..pack.js gzip 844 B 844 B
Overall change 1 kB 1 kB
Next Runtimes
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
973-experime...dev.js gzip 322 B 322 B
973.runtime.dev.js gzip 314 B 314 B
app-page-exp...dev.js gzip 317 kB 317 kB
app-page-exp..prod.js gzip 121 kB 121 kB
app-page-tur..prod.js gzip 134 kB 134 kB
app-page-tur..prod.js gzip 129 kB 129 kB
app-page.run...dev.js gzip 307 kB 307 kB
app-page.run..prod.js gzip 117 kB 117 kB
app-route-ex...dev.js gzip 35.9 kB 35.9 kB
app-route-ex..prod.js gzip 24.4 kB 24.4 kB
app-route-tu..prod.js gzip 24.4 kB 24.4 kB
app-route-tu..prod.js gzip 24.1 kB 24.1 kB
app-route.ru...dev.js gzip 37.5 kB 37.5 kB
app-route.ru..prod.js gzip 24.1 kB 24.1 kB
pages-api-tu..prod.js gzip 9.61 kB 9.61 kB
pages-api.ru...dev.js gzip 11.4 kB 11.4 kB
pages-api.ru..prod.js gzip 9.61 kB 9.61 kB
pages-turbo...prod.js gzip 20.9 kB 20.9 kB
pages.runtim...dev.js gzip 26.5 kB 26.5 kB
pages.runtim..prod.js gzip 20.9 kB 20.9 kB
server.runti..prod.js gzip 58.3 kB 58.3 kB
Overall change 1.45 MB 1.45 MB
build cache Overall increase ⚠️
vercel/next.js canary vercel/next.js kdy1/ts-facade-module-ident Change
0.pack gzip 1.84 MB 1.85 MB ⚠️ +4.32 kB
index.pack gzip 142 kB 143 kB ⚠️ +879 B
Overall change 1.99 MB 1.99 MB ⚠️ +5.2 kB
Diff details
Diff for page.js
@@ -15,7 +15,7 @@
       /***/
     },
 
-    /***/ 9355: /***/ (
+    /***/ 2486: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -30,7 +30,7 @@
         default: () => /* binding */ nHandler,
       });
 
-      // NAMESPACE OBJECT: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/build/webpack/loaders/next-app-loader/index.js?name=app%2Fapp-edge-ssr%2Fpage&page=%2Fapp-edge-ssr%2Fpage&pagePath=private-next-app-dir%2Fapp-edge-ssr%2Fpage.js&appDir=%2Ftmp%2Fnext-statsFIAaIG%2Fstats-app%2Fapp&appPaths=%2Fapp-edge-ssr%2Fpage&pageExtensions=tsx&pageExtensions=ts&pageExtensions=jsx&pageExtensions=js&basePath=&assetPrefix=&nextConfigOutput=&flyingShuttle=false&preferredRegion=&middlewareConfig=e30%3D!./app/app-edge-ssr/page.js?__next_edge_ssr_entry__
+      // NAMESPACE OBJECT: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/build/webpack/loaders/next-app-loader/index.js?name=app%2Fapp-edge-ssr%2Fpage&page=%2Fapp-edge-ssr%2Fpage&pagePath=private-next-app-dir%2Fapp-edge-ssr%2Fpage.js&appDir=%2Ftmp%2Fnext-statsFIAaIG%2Fstats-app%2Fapp&appPaths=%2Fapp-edge-ssr%2Fpage&pageExtensions=tsx&pageExtensions=ts&pageExtensions=jsx&pageExtensions=js&basePath=&assetPrefix=&nextConfigOutput=&flyingShuttle=false&preferredRegion=&middlewareConfig=e30%3D!./app/app-edge-ssr/page.js?__next_edge_ssr_entry__
       var page_next_edge_ssr_entry_namespaceObject = {};
       __webpack_require__.r(page_next_edge_ssr_entry_namespaceObject);
       __webpack_require__.d(page_next_edge_ssr_entry_namespaceObject, {
@@ -82,35 +82,35 @@
         workUnitAsyncStorage: () => entry_base /* workUnitAsyncStorage */.Sz,
       });
 
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/web/globals.js
-      var globals = __webpack_require__(341);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/web/adapter.js + 3 modules
-      var adapter = __webpack_require__(7977);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/build/webpack/loaders/next-edge-ssr-loader/render.js + 85 modules
-      var render = __webpack_require__(6616);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/lib/incremental-cache/index.js + 5 modules
-      var incremental_cache = __webpack_require__(6652);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/app-render/app-render.js + 63 modules
-      var app_render = __webpack_require__(5606);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/route-modules/app-page/module.compiled.js
-      var module_compiled = __webpack_require__(620);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/route-kind.js
-      var route_kind = __webpack_require__(8573);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/client/components/error-boundary.js
-      var error_boundary = __webpack_require__(5774);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/app-render/entry-base.js + 29 modules
-      var entry_base = __webpack_require__(5174); // CONCATENATED MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/build/webpack/loaders/next-app-loader/index.js?name=app%2Fapp-edge-ssr%2Fpage&page=%2Fapp-edge-ssr%2Fpage&pagePath=private-next-app-dir%2Fapp-edge-ssr%2Fpage.js&appDir=%2Ftmp%2Fnext-statsFIAaIG%2Fstats-app%2Fapp&appPaths=%2Fapp-edge-ssr%2Fpage&pageExtensions=tsx&pageExtensions=ts&pageExtensions=jsx&pageExtensions=js&basePath=&assetPrefix=&nextConfigOutput=&flyingShuttle=false&preferredRegion=&middlewareConfig=e30%3D!./app/app-edge-ssr/page.js?__next_edge_ssr_entry__
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/web/globals.js
+      var globals = __webpack_require__(9156);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/web/adapter.js + 3 modules
+      var adapter = __webpack_require__(5723);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/build/webpack/loaders/next-edge-ssr-loader/render.js + 85 modules
+      var render = __webpack_require__(8935);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/lib/incremental-cache/index.js + 5 modules
+      var incremental_cache = __webpack_require__(7771);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/app-render/app-render.js + 63 modules
+      var app_render = __webpack_require__(9559);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/route-modules/app-page/module.compiled.js
+      var module_compiled = __webpack_require__(7601);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/route-kind.js
+      var route_kind = __webpack_require__(5655);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/client/components/error-boundary.js
+      var error_boundary = __webpack_require__(5847);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/app-render/entry-base.js + 29 modules
+      var entry_base = __webpack_require__(2393); // CONCATENATED MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/build/webpack/loaders/next-app-loader/index.js?name=app%2Fapp-edge-ssr%2Fpage&page=%2Fapp-edge-ssr%2Fpage&pagePath=private-next-app-dir%2Fapp-edge-ssr%2Fpage.js&appDir=%2Ftmp%2Fnext-statsFIAaIG%2Fstats-app%2Fapp&appPaths=%2Fapp-edge-ssr%2Fpage&pageExtensions=tsx&pageExtensions=ts&pageExtensions=jsx&pageExtensions=js&basePath=&assetPrefix=&nextConfigOutput=&flyingShuttle=false&preferredRegion=&middlewareConfig=e30%3D!./app/app-edge-ssr/page.js?__next_edge_ssr_entry__
       const module0 = () =>
         Promise.resolve(/* import() eager */).then(
-          __webpack_require__.bind(__webpack_require__, 8827)
+          __webpack_require__.bind(__webpack_require__, 4114)
         );
       const module1 = () =>
         Promise.resolve(/* import() eager */).then(
-          __webpack_require__.bind(__webpack_require__, 5435)
+          __webpack_require__.bind(__webpack_require__, 3641)
         );
       const page2 = () =>
         Promise.resolve(/* import() eager */).then(
-          __webpack_require__.bind(__webpack_require__, 4270)
+          __webpack_require__.bind(__webpack_require__, 8250)
         );
 
       // We inject the tree and pages here so that we can use them in the route
@@ -173,12 +173,12 @@
       });
 
       //# sourceMappingURL=app-page.js.map
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/lib/page-types.js
-      var page_types = __webpack_require__(7765);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/app-render/encryption-utils.js
-      var encryption_utils = __webpack_require__(2676);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/esm/server/app-render/action-utils.js
-      var action_utils = __webpack_require__(1240); // CONCATENATED MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/dist/build/webpack/loaders/next-edge-ssr-loader/index.js?{"absolute500Path":"","absoluteAppPath":"next/dist/pages/_app","absoluteDocumentPath":"next/dist/pages/_document","absoluteErrorPath":"next/dist/pages/_error","absolutePagePath":"private-next-app-dir/app-edge-ssr/page.js","dev":false,"isServerComponent":true,"page":"/app-edge-ssr/page","stringifiedConfig":"eyJlbnYiOnt9LCJlc2xpbnQiOnsiaWdub3JlRHVyaW5nQnVpbGRzIjpmYWxzZX0sInR5cGVzY3JpcHQiOnsiaWdub3JlQnVpbGRFcnJvcnMiOmZhbHNlLCJ0c2NvbmZpZ1BhdGgiOiJ0c2NvbmZpZy5qc29uIn0sImRpc3REaXIiOiIubmV4dCIsImNsZWFuRGlzdERpciI6dHJ1ZSwiYXNzZXRQcmVmaXgiOiIiLCJjYWNoZU1heE1lbW9yeVNpemUiOjUyNDI4ODAwLCJjb25maWdPcmlnaW4iOiJuZXh0LmNvbmZpZy5qcyIsInVzZUZpbGVTeXN0ZW1QdWJsaWNSb3V0ZXMiOnRydWUsImdlbmVyYXRlRXRhZ3MiOnRydWUsInBhZ2VFeHRlbnNpb25zIjpbInRzeCIsInRzIiwianN4IiwianMiXSwicG93ZXJlZEJ5SGVhZGVyIjp0cnVlLCJjb21wcmVzcyI6dHJ1ZSwiaW1hZ2VzIjp7ImRldmljZVNpemVzIjpbNjQwLDc1MCw4MjgsMTA4MCwxMjAwLDE5MjAsMjA0OCwzODQwXSwiaW1hZ2VTaXplcyI6WzE2LDMyLDQ4LDY0LDk2LDEyOCwyNTYsMzg0XSwicGF0aCI6Ii9fbmV4dC9pbWFnZSIsImxvYWRlciI6ImRlZmF1bHQiLCJsb2FkZXJGaWxlIjoiIiwiZG9tYWlucyI6W10sImRpc2FibGVTdGF0aWNJbWFnZXMiOmZhbHNlLCJtaW5pbXVtQ2FjaGVUVEwiOjYwLCJmb3JtYXRzIjpbImltYWdlL3dlYnAiXSwiZGFuZ2Vyb3VzbHlBbGxvd1NWRyI6ZmFsc2UsImNvbnRlbnRTZWN1cml0eVBvbGljeSI6InNjcmlwdC1zcmMgJ25vbmUnOyBmcmFtZS1zcmMgJ25vbmUnOyBzYW5kYm94OyIsImNvbnRlbnREaXNwb3NpdGlvblR5cGUiOiJhdHRhY2htZW50IiwicmVtb3RlUGF0dGVybnMiOltdLCJ1bm9wdGltaXplZCI6ZmFsc2V9LCJkZXZJbmRpY2F0b3JzIjp7ImFwcElzclN0YXR1cyI6dHJ1ZSwiYnVpbGRBY3Rpdml0eSI6dHJ1ZSwiYnVpbGRBY3Rpdml0eVBvc2l0aW9uIjoiYm90dG9tLXJpZ2h0In0sIm9uRGVtYW5kRW50cmllcyI6eyJtYXhJbmFjdGl2ZUFnZSI6NjAwMDAsInBhZ2VzQnVmZmVyTGVuZ3RoIjo1fSwiYW1wIjp7ImNhbm9uaWNhbEJhc2UiOiIifSwiYmFzZVBhdGgiOiIiLCJzYXNzT3B0aW9ucyI6e30sInRyYWlsaW5nU2xhc2giOmZhbHNlLCJpMThuIjpudWxsLCJwcm9kdWN0aW9uQnJvd3NlclNvdXJjZU1hcHMiOmZhbHNlLCJleGNsdWRlRGVmYXVsdE1vbWVudExvY2FsZXMiOnRydWUsInNlcnZlclJ1bnRpbWVDb25maWciOnt9LCJwdWJsaWNSdW50aW1lQ29uZmlnIjp7fSwicmVhY3RQcm9kdWN0aW9uUHJvZmlsaW5nIjpmYWxzZSwicmVhY3RTdHJpY3RNb2RlIjpudWxsLCJyZWFjdE1heEhlYWRlcnNMZW5ndGgiOjYwMDAsImh0dHBBZ2VudE9wdGlvbnMiOnsia2VlcEFsaXZlIjp0cnVlfSwibG9nZ2luZyI6e30sImV4cGlyZVRpbWUiOjMxNTM2MDAwLCJzdGF0aWNQYWdlR2VuZXJhdGlvblRpbWVvdXQiOjYwLCJtb2R1bGFyaXplSW1wb3J0cyI6eyJAbXVpL2ljb25zLW1hdGVyaWFsIjp7InRyYW5zZm9ybSI6IkBtdWkvaWNvbnMtbWF0ZXJpYWwve3ttZW1iZXJ9fSJ9LCJsb2Rhc2giOnsidHJhbnNmb3JtIjoibG9kYXNoL3t7bWVtYmVyfX0ifX0sIm91dHB1dEZpbGVUcmFjaW5nUm9vdCI6Ii90bXAvbmV4dC1zdGF0c0ZJQWFJRy9zdGF0cy1hcHAiLCJleHBlcmltZW50YWwiOnsiY2FjaGVMaWZlIjp7ImRlZmF1bHQiOnsic3RhbGUiOjMwMCwicmV2YWxpZGF0ZSI6OTAwLCJleHBpcmUiOjQyOTQ5NjcyOTR9LCJzZWNvbmRzIjp7InN0YWxlIjowLCJyZXZhbGlkYXRlIjoxLCJleHBpcmUiOjF9LCJtaW51dGVzIjp7InN0YWxlIjozMDAsInJldmFsaWRhdGUiOjYwLCJleHBpcmUiOjM2MDB9LCJob3VycyI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjozNjAwLCJleHBpcmUiOjg2NDAwfSwiZGF5cyI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjo4NjQwMCwiZXhwaXJlIjo2MDQ4MDB9LCJ3ZWVrcyI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjo2MDQ4MDAsImV4cGlyZSI6MjU5MjAwMH0sIm1heCI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjoyNTkyMDAwLCJleHBpcmUiOjQyOTQ5NjcyOTR9fSwiY2FjaGVIYW5kbGVycyI6e30sIm11bHRpWm9uZURyYWZ0TW9kZSI6ZmFsc2UsImFwcE5hdkZhaWxIYW5kbGluZyI6ZmFsc2UsInByZXJlbmRlckVhcmx5RXhpdCI6dHJ1ZSwic2VydmVyTWluaWZpY2F0aW9uIjp0cnVlLCJzZXJ2ZXJTb3VyY2VNYXBzIjpmYWxzZSwibGlua05vVG91Y2hTdGFydCI6ZmFsc2UsImNhc2VTZW5zaXRpdmVSb3V0ZXMiOmZhbHNlLCJwcmVsb2FkRW50cmllc09uU3RhcnQiOnRydWUsImNsaWVudFJvdXRlckZpbHRlciI6dHJ1ZSwiY2xpZW50Um91dGVyRmlsdGVyUmVkaXJlY3RzIjpmYWxzZSwiZmV0Y2hDYWNoZUtleVByZWZpeCI6IiIsIm1pZGRsZXdhcmVQcmVmZXRjaCI6ImZsZXhpYmxlIiwib3B0aW1pc3RpY0NsaWVudENhY2hlIjp0cnVlLCJtYW51YWxDbGllbnRCYXNlUGF0aCI6ZmFsc2UsImNwdXMiOjE5LCJtZW1vcnlCYXNlZFdvcmtlcnNDb3VudCI6ZmFsc2UsImlzckZsdXNoVG9EaXNrIjp0cnVlLCJ3b3JrZXJUaHJlYWRzIjpmYWxzZSwib3B0aW1pemVDc3MiOmZhbHNlLCJuZXh0U2NyaXB0V29ya2VycyI6ZmFsc2UsInNjcm9sbFJlc3RvcmF0aW9uIjpmYWxzZSwiZXh0ZXJuYWxEaXIiOmZhbHNlLCJkaXNhYmxlT3B0aW1pemVkTG9hZGluZyI6ZmFsc2UsImd6aXBTaXplIjp0cnVlLCJjcmFDb21wYXQiOmZhbHNlLCJlc21FeHRlcm5hbHMiOnRydWUsImZ1bGx5U3BlY2lmaWVkIjpmYWxzZSwic3djVHJhY2VQcm9maWxpbmciOmZhbHNlLCJmb3JjZVN3Y1RyYW5zZm9ybXMiOmZhbHNlLCJsYXJnZVBhZ2VEYXRhQnl0ZXMiOjEyODAwMCwidHVyYm8iOnsicm9vdCI6Ii90bXAvbmV4dC1zdGF0c0ZJQWFJRy9zdGF0cy1hcHAifSwidHlwZWRSb3V0ZXMiOmZhbHNlLCJ0eXBlZEVudiI6ZmFsc2UsInBhcmFsbGVsU2VydmVyQ29tcGlsZXMiOmZhbHNlLCJwYXJhbGxlbFNlcnZlckJ1aWxkVHJhY2VzIjpmYWxzZSwicHByIjpmYWxzZSwid2VicGFja01lbW9yeU9wdGltaXphdGlvbnMiOmZhbHNlLCJvcHRpbWl6ZVNlcnZlclJlYWN0Ijp0cnVlLCJ1c2VFYXJseUltcG9ydCI6ZmFsc2UsInN0YWxlVGltZXMiOnsiZHluYW1pYyI6MCwic3RhdGljIjozMDB9LCJhZnRlciI6ZmFsc2UsInNlcnZlckNvbXBvbmVudHNIbXJDYWNoZSI6dHJ1ZSwic3RhdGljR2VuZXJhdGlvbk1heENvbmN1cnJlbmN5Ijo4LCJzdGF0aWNHZW5lcmF0aW9uTWluUGFnZXNQZXJXb3JrZXIiOjI1LCJkeW5hbWljSU8iOmZhbHNlLCJvcHRpbWl6ZVBhY2thZ2VJbXBvcnRzIjpbImx1Y2lkZS1yZWFjdCIsImRhdGUtZm5zIiwibG9kYXNoLWVzIiwicmFtZGEiLCJhbnRkIiwicmVhY3QtYm9vdHN0cmFwIiwiYWhvb2tzIiwiQGFudC1kZXNpZ24vaWNvbnMiLCJAaGVhZGxlc3N1aS9yZWFjdCIsIkBoZWFkbGVzc3VpLWZsb2F0L3JlYWN0IiwiQGhlcm9pY29ucy9yZWFjdC8yMC9zb2xpZCIsIkBoZXJvaWNvbnMvcmVhY3QvMjQvc29saWQiLCJAaGVyb2ljb25zL3JlYWN0LzI0L291dGxpbmUiLCJAdmlzeC92aXN4IiwiQHRyZW1vci9yZWFjdCIsInJ4anMiLCJAbXVpL21hdGVyaWFsIiwiQG11aS9pY29ucy1tYXRlcmlhbCIsInJlY2hhcnRzIiwicmVhY3QtdXNlIiwiZWZmZWN0IiwiQGVmZmVjdC9zY2hlbWEiLCJAZWZmZWN0L3BsYXRmb3JtIiwiQGVmZmVjdC9wbGF0Zm9ybS1ub2RlIiwiQGVmZmVjdC9wbGF0Zm9ybS1icm93c2VyIiwiQGVmZmVjdC9wbGF0Zm9ybS1idW4iLCJAZWZmZWN0L3NxbCIsIkBlZmZlY3Qvc3FsLW1zc3FsIiwiQGVmZmVjdC9zcWwtbXlzcWwyIiwiQGVmZmVjdC9zcWwtcGciLCJAZWZmZWN0L3NxbC1zcXVsaXRlLW5vZGUiLCJAZWZmZWN0L3NxbC1zcXVsaXRlLWJ1biIsIkBlZmZlY3Qvc3FsLXNxdWxpdGUtd2FzbSIsIkBlZmZlY3Qvc3FsLXNxdWxpdGUtcmVhY3QtbmF0aXZlIiwiQGVmZmVjdC9ycGMiLCJAZWZmZWN0L3JwYy1odHRwIiwiQGVmZmVjdC90eXBlY2xhc3MiLCJAZWZmZWN0L2V4cGVyaW1lbnRhbCIsIkBlZmZlY3Qvb3BlbnRlbGVtZXRyeSIsIkBtYXRlcmlhbC11aS9jb3JlIiwiQG1hdGVyaWFsLXVpL2ljb25zIiwiQHRhYmxlci9pY29ucy1yZWFjdCIsIm11aS1jb3JlIiwicmVhY3QtaWNvbnMvYWkiLCJyZWFjdC1pY29ucy9iaSIsInJlYWN0LWljb25zL2JzIiwicmVhY3QtaWNvbnMvY2ciLCJyZWFjdC1pY29ucy9jaSIsInJlYWN0LWljb25zL2RpIiwicmVhY3QtaWNvbnMvZmEiLCJyZWFjdC1pY29ucy9mYTYiLCJyZWFjdC1pY29ucy9mYyIsInJlYWN0LWljb25zL2ZpIiwicmVhY3QtaWNvbnMvZ2kiLCJyZWFjdC1pY29ucy9nbyIsInJlYWN0LWljb25zL2dyIiwicmVhY3QtaWNvbnMvaGkiLCJyZWFjdC1pY29ucy9oaTIiLCJyZWFjdC1pY29ucy9pbSIsInJlYWN0LWljb25zL2lvIiwicmVhY3QtaWNvbnMvaW81IiwicmVhY3QtaWNvbnMvbGlhIiwicmVhY3QtaWNvbnMvbGliIiwicmVhY3QtaWNvbnMvbHUiLCJyZWFjdC1pY29ucy9tZCIsInJlYWN0LWljb25zL3BpIiwicmVhY3QtaWNvbnMvcmkiLCJyZWFjdC1pY29ucy9yeCIsInJlYWN0LWljb25zL3NpIiwicmVhY3QtaWNvbnMvc2wiLCJyZWFjdC1pY29ucy90YiIsInJlYWN0LWljb25zL3RmaSIsInJlYWN0LWljb25zL3RpIiwicmVhY3QtaWNvbnMvdnNjIiwicmVhY3QtaWNvbnMvd2kiXX0sImJ1bmRsZVBhZ2VzUm91dGVyRGVwZW5kZW5jaWVzIjpmYWxzZSwiY29uZmlnRmlsZSI6Ii90bXAvbmV4dC1zdGF0c0ZJQWFJRy9zdGF0cy1hcHAvbmV4dC5jb25maWcuanMiLCJjb25maWdGaWxlTmFtZSI6Im5leHQuY29uZmlnLmpzIn0=","pagesType":"app","appDirLoader":"bmV4dC1hcHAtbG9hZGVyP25hbWU9YXBwJTJGYXBwLWVkZ2Utc3NyJTJGcGFnZSZwYWdlPSUyRmFwcC1lZGdlLXNzciUyRnBhZ2UmcGFnZVBhdGg9cHJpdmF0ZS1uZXh0LWFwcC1kaXIlMkZhcHAtZWRnZS1zc3IlMkZwYWdlLmpzJmFwcERpcj0lMkZ0bXAlMkZuZXh0LXN0YXRzRklBYUlHJTJGc3RhdHMtYXBwJTJGYXBwJmFwcFBhdGhzPSUyRmFwcC1lZGdlLXNzciUyRnBhZ2UmcGFnZUV4dGVuc2lvbnM9dHN4JnBhZ2VFeHRlbnNpb25zPXRzJnBhZ2VFeHRlbnNpb25zPWpzeCZwYWdlRXh0ZW5zaW9ucz1qcyZiYXNlUGF0aD0mYXNzZXRQcmVmaXg9Jm5leHRDb25maWdPdXRwdXQ9JmZseWluZ1NodXR0bGU9ZmFsc2UmcHJlZmVycmVkUmVnaW9uPSZtaWRkbGV3YXJlQ29uZmlnPWUzMCUzRCE=","sriEnabled":false,"middlewareConfig":"e30=","cacheHandlers":"{}"}!
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/lib/page-types.js
+      var page_types = __webpack_require__(2676);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/app-render/encryption-utils.js
+      var encryption_utils = __webpack_require__(2306);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/esm/server/app-render/action-utils.js
+      var action_utils = __webpack_require__(3631); // CONCATENATED MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/dist/build/webpack/loaders/next-edge-ssr-loader/index.js?{"absolute500Path":"","absoluteAppPath":"next/dist/pages/_app","absoluteDocumentPath":"next/dist/pages/_document","absoluteErrorPath":"next/dist/pages/_error","absolutePagePath":"private-next-app-dir/app-edge-ssr/page.js","dev":false,"isServerComponent":true,"page":"/app-edge-ssr/page","stringifiedConfig":"eyJlbnYiOnt9LCJlc2xpbnQiOnsiaWdub3JlRHVyaW5nQnVpbGRzIjpmYWxzZX0sInR5cGVzY3JpcHQiOnsiaWdub3JlQnVpbGRFcnJvcnMiOmZhbHNlLCJ0c2NvbmZpZ1BhdGgiOiJ0c2NvbmZpZy5qc29uIn0sImRpc3REaXIiOiIubmV4dCIsImNsZWFuRGlzdERpciI6dHJ1ZSwiYXNzZXRQcmVmaXgiOiIiLCJjYWNoZU1heE1lbW9yeVNpemUiOjUyNDI4ODAwLCJjb25maWdPcmlnaW4iOiJuZXh0LmNvbmZpZy5qcyIsInVzZUZpbGVTeXN0ZW1QdWJsaWNSb3V0ZXMiOnRydWUsImdlbmVyYXRlRXRhZ3MiOnRydWUsInBhZ2VFeHRlbnNpb25zIjpbInRzeCIsInRzIiwianN4IiwianMiXSwicG93ZXJlZEJ5SGVhZGVyIjp0cnVlLCJjb21wcmVzcyI6dHJ1ZSwiaW1hZ2VzIjp7ImRldmljZVNpemVzIjpbNjQwLDc1MCw4MjgsMTA4MCwxMjAwLDE5MjAsMjA0OCwzODQwXSwiaW1hZ2VTaXplcyI6WzE2LDMyLDQ4LDY0LDk2LDEyOCwyNTYsMzg0XSwicGF0aCI6Ii9fbmV4dC9pbWFnZSIsImxvYWRlciI6ImRlZmF1bHQiLCJsb2FkZXJGaWxlIjoiIiwiZG9tYWlucyI6W10sImRpc2FibGVTdGF0aWNJbWFnZXMiOmZhbHNlLCJtaW5pbXVtQ2FjaGVUVEwiOjYwLCJmb3JtYXRzIjpbImltYWdlL3dlYnAiXSwiZGFuZ2Vyb3VzbHlBbGxvd1NWRyI6ZmFsc2UsImNvbnRlbnRTZWN1cml0eVBvbGljeSI6InNjcmlwdC1zcmMgJ25vbmUnOyBmcmFtZS1zcmMgJ25vbmUnOyBzYW5kYm94OyIsImNvbnRlbnREaXNwb3NpdGlvblR5cGUiOiJhdHRhY2htZW50IiwicmVtb3RlUGF0dGVybnMiOltdLCJ1bm9wdGltaXplZCI6ZmFsc2V9LCJkZXZJbmRpY2F0b3JzIjp7ImFwcElzclN0YXR1cyI6dHJ1ZSwiYnVpbGRBY3Rpdml0eSI6dHJ1ZSwiYnVpbGRBY3Rpdml0eVBvc2l0aW9uIjoiYm90dG9tLXJpZ2h0In0sIm9uRGVtYW5kRW50cmllcyI6eyJtYXhJbmFjdGl2ZUFnZSI6NjAwMDAsInBhZ2VzQnVmZmVyTGVuZ3RoIjo1fSwiYW1wIjp7ImNhbm9uaWNhbEJhc2UiOiIifSwiYmFzZVBhdGgiOiIiLCJzYXNzT3B0aW9ucyI6e30sInRyYWlsaW5nU2xhc2giOmZhbHNlLCJpMThuIjpudWxsLCJwcm9kdWN0aW9uQnJvd3NlclNvdXJjZU1hcHMiOmZhbHNlLCJleGNsdWRlRGVmYXVsdE1vbWVudExvY2FsZXMiOnRydWUsInNlcnZlclJ1bnRpbWVDb25maWciOnt9LCJwdWJsaWNSdW50aW1lQ29uZmlnIjp7fSwicmVhY3RQcm9kdWN0aW9uUHJvZmlsaW5nIjpmYWxzZSwicmVhY3RTdHJpY3RNb2RlIjpudWxsLCJyZWFjdE1heEhlYWRlcnNMZW5ndGgiOjYwMDAsImh0dHBBZ2VudE9wdGlvbnMiOnsia2VlcEFsaXZlIjp0cnVlfSwibG9nZ2luZyI6e30sImV4cGlyZVRpbWUiOjMxNTM2MDAwLCJzdGF0aWNQYWdlR2VuZXJhdGlvblRpbWVvdXQiOjYwLCJtb2R1bGFyaXplSW1wb3J0cyI6eyJAbXVpL2ljb25zLW1hdGVyaWFsIjp7InRyYW5zZm9ybSI6IkBtdWkvaWNvbnMtbWF0ZXJpYWwve3ttZW1iZXJ9fSJ9LCJsb2Rhc2giOnsidHJhbnNmb3JtIjoibG9kYXNoL3t7bWVtYmVyfX0ifX0sIm91dHB1dEZpbGVUcmFjaW5nUm9vdCI6Ii90bXAvbmV4dC1zdGF0c0ZJQWFJRy9zdGF0cy1hcHAiLCJleHBlcmltZW50YWwiOnsiY2FjaGVMaWZlIjp7ImRlZmF1bHQiOnsic3RhbGUiOjMwMCwicmV2YWxpZGF0ZSI6OTAwLCJleHBpcmUiOjQyOTQ5NjcyOTR9LCJzZWNvbmRzIjp7InN0YWxlIjowLCJyZXZhbGlkYXRlIjoxLCJleHBpcmUiOjF9LCJtaW51dGVzIjp7InN0YWxlIjozMDAsInJldmFsaWRhdGUiOjYwLCJleHBpcmUiOjM2MDB9LCJob3VycyI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjozNjAwLCJleHBpcmUiOjg2NDAwfSwiZGF5cyI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjo4NjQwMCwiZXhwaXJlIjo2MDQ4MDB9LCJ3ZWVrcyI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjo2MDQ4MDAsImV4cGlyZSI6MjU5MjAwMH0sIm1heCI6eyJzdGFsZSI6MzAwLCJyZXZhbGlkYXRlIjoyNTkyMDAwLCJleHBpcmUiOjQyOTQ5NjcyOTR9fSwiY2FjaGVIYW5kbGVycyI6e30sIm11bHRpWm9uZURyYWZ0TW9kZSI6ZmFsc2UsImFwcE5hdkZhaWxIYW5kbGluZyI6ZmFsc2UsInByZXJlbmRlckVhcmx5RXhpdCI6dHJ1ZSwic2VydmVyTWluaWZpY2F0aW9uIjp0cnVlLCJzZXJ2ZXJTb3VyY2VNYXBzIjpmYWxzZSwibGlua05vVG91Y2hTdGFydCI6ZmFsc2UsImNhc2VTZW5zaXRpdmVSb3V0ZXMiOmZhbHNlLCJwcmVsb2FkRW50cmllc09uU3RhcnQiOnRydWUsImNsaWVudFJvdXRlckZpbHRlciI6dHJ1ZSwiY2xpZW50Um91dGVyRmlsdGVyUmVkaXJlY3RzIjpmYWxzZSwiZmV0Y2hDYWNoZUtleVByZWZpeCI6IiIsIm1pZGRsZXdhcmVQcmVmZXRjaCI6ImZsZXhpYmxlIiwib3B0aW1pc3RpY0NsaWVudENhY2hlIjp0cnVlLCJtYW51YWxDbGllbnRCYXNlUGF0aCI6ZmFsc2UsImNwdXMiOjE5LCJtZW1vcnlCYXNlZFdvcmtlcnNDb3VudCI6ZmFsc2UsImlzckZsdXNoVG9EaXNrIjp0cnVlLCJ3b3JrZXJUaHJlYWRzIjpmYWxzZSwib3B0aW1pemVDc3MiOmZhbHNlLCJuZXh0U2NyaXB0V29ya2VycyI6ZmFsc2UsInNjcm9sbFJlc3RvcmF0aW9uIjpmYWxzZSwiZXh0ZXJuYWxEaXIiOmZhbHNlLCJkaXNhYmxlT3B0aW1pemVkTG9hZGluZyI6ZmFsc2UsImd6aXBTaXplIjp0cnVlLCJjcmFDb21wYXQiOmZhbHNlLCJlc21FeHRlcm5hbHMiOnRydWUsImZ1bGx5U3BlY2lmaWVkIjpmYWxzZSwic3djVHJhY2VQcm9maWxpbmciOmZhbHNlLCJmb3JjZVN3Y1RyYW5zZm9ybXMiOmZhbHNlLCJsYXJnZVBhZ2VEYXRhQnl0ZXMiOjEyODAwMCwidHVyYm8iOnsicm9vdCI6Ii90bXAvbmV4dC1zdGF0c0ZJQWFJRy9zdGF0cy1hcHAifSwidHlwZWRSb3V0ZXMiOmZhbHNlLCJ0eXBlZEVudiI6ZmFsc2UsInBhcmFsbGVsU2VydmVyQ29tcGlsZXMiOmZhbHNlLCJwYXJhbGxlbFNlcnZlckJ1aWxkVHJhY2VzIjpmYWxzZSwicHByIjpmYWxzZSwid2VicGFja01lbW9yeU9wdGltaXphdGlvbnMiOmZhbHNlLCJvcHRpbWl6ZVNlcnZlclJlYWN0Ijp0cnVlLCJ1c2VFYXJseUltcG9ydCI6ZmFsc2UsInN0YWxlVGltZXMiOnsiZHluYW1pYyI6MCwic3RhdGljIjozMDB9LCJhZnRlciI6ZmFsc2UsInNlcnZlckNvbXBvbmVudHNIbXJDYWNoZSI6dHJ1ZSwic3RhdGljR2VuZXJhdGlvbk1heENvbmN1cnJlbmN5Ijo4LCJzdGF0aWNHZW5lcmF0aW9uTWluUGFnZXNQZXJXb3JrZXIiOjI1LCJkeW5hbWljSU8iOmZhbHNlLCJvcHRpbWl6ZVBhY2thZ2VJbXBvcnRzIjpbImx1Y2lkZS1yZWFjdCIsImRhdGUtZm5zIiwibG9kYXNoLWVzIiwicmFtZGEiLCJhbnRkIiwicmVhY3QtYm9vdHN0cmFwIiwiYWhvb2tzIiwiQGFudC1kZXNpZ24vaWNvbnMiLCJAaGVhZGxlc3N1aS9yZWFjdCIsIkBoZWFkbGVzc3VpLWZsb2F0L3JlYWN0IiwiQGhlcm9pY29ucy9yZWFjdC8yMC9zb2xpZCIsIkBoZXJvaWNvbnMvcmVhY3QvMjQvc29saWQiLCJAaGVyb2ljb25zL3JlYWN0LzI0L291dGxpbmUiLCJAdmlzeC92aXN4IiwiQHRyZW1vci9yZWFjdCIsInJ4anMiLCJAbXVpL21hdGVyaWFsIiwiQG11aS9pY29ucy1tYXRlcmlhbCIsInJlY2hhcnRzIiwicmVhY3QtdXNlIiwiZWZmZWN0IiwiQGVmZmVjdC9zY2hlbWEiLCJAZWZmZWN0L3BsYXRmb3JtIiwiQGVmZmVjdC9wbGF0Zm9ybS1ub2RlIiwiQGVmZmVjdC9wbGF0Zm9ybS1icm93c2VyIiwiQGVmZmVjdC9wbGF0Zm9ybS1idW4iLCJAZWZmZWN0L3NxbCIsIkBlZmZlY3Qvc3FsLW1zc3FsIiwiQGVmZmVjdC9zcWwtbXlzcWwyIiwiQGVmZmVjdC9zcWwtcGciLCJAZWZmZWN0L3NxbC1zcXVsaXRlLW5vZGUiLCJAZWZmZWN0L3NxbC1zcXVsaXRlLWJ1biIsIkBlZmZlY3Qvc3FsLXNxdWxpdGUtd2FzbSIsIkBlZmZlY3Qvc3FsLXNxdWxpdGUtcmVhY3QtbmF0aXZlIiwiQGVmZmVjdC9ycGMiLCJAZWZmZWN0L3JwYy1odHRwIiwiQGVmZmVjdC90eXBlY2xhc3MiLCJAZWZmZWN0L2V4cGVyaW1lbnRhbCIsIkBlZmZlY3Qvb3BlbnRlbGVtZXRyeSIsIkBtYXRlcmlhbC11aS9jb3JlIiwiQG1hdGVyaWFsLXVpL2ljb25zIiwiQHRhYmxlci9pY29ucy1yZWFjdCIsIm11aS1jb3JlIiwicmVhY3QtaWNvbnMvYWkiLCJyZWFjdC1pY29ucy9iaSIsInJlYWN0LWljb25zL2JzIiwicmVhY3QtaWNvbnMvY2ciLCJyZWFjdC1pY29ucy9jaSIsInJlYWN0LWljb25zL2RpIiwicmVhY3QtaWNvbnMvZmEiLCJyZWFjdC1pY29ucy9mYTYiLCJyZWFjdC1pY29ucy9mYyIsInJlYWN0LWljb25zL2ZpIiwicmVhY3QtaWNvbnMvZ2kiLCJyZWFjdC1pY29ucy9nbyIsInJlYWN0LWljb25zL2dyIiwicmVhY3QtaWNvbnMvaGkiLCJyZWFjdC1pY29ucy9oaTIiLCJyZWFjdC1pY29ucy9pbSIsInJlYWN0LWljb25zL2lvIiwicmVhY3QtaWNvbnMvaW81IiwicmVhY3QtaWNvbnMvbGlhIiwicmVhY3QtaWNvbnMvbGliIiwicmVhY3QtaWNvbnMvbHUiLCJyZWFjdC1pY29ucy9tZCIsInJlYWN0LWljb25zL3BpIiwicmVhY3QtaWNvbnMvcmkiLCJyZWFjdC1pY29ucy9yeCIsInJlYWN0LWljb25zL3NpIiwicmVhY3QtaWNvbnMvc2wiLCJyZWFjdC1pY29ucy90YiIsInJlYWN0LWljb25zL3RmaSIsInJlYWN0LWljb25zL3RpIiwicmVhY3QtaWNvbnMvdnNjIiwicmVhY3QtaWNvbnMvd2kiXX0sImJ1bmRsZVBhZ2VzUm91dGVyRGVwZW5kZW5jaWVzIjpmYWxzZSwiY29uZmlnRmlsZSI6Ii90bXAvbmV4dC1zdGF0c0ZJQWFJRy9zdGF0cy1hcHAvbmV4dC5jb25maWcuanMiLCJjb25maWdGaWxlTmFtZSI6Im5leHQuY29uZmlnLmpzIn0=","pagesType":"app","appDirLoader":"bmV4dC1hcHAtbG9hZGVyP25hbWU9YXBwJTJGYXBwLWVkZ2Utc3NyJTJGcGFnZSZwYWdlPSUyRmFwcC1lZGdlLXNzciUyRnBhZ2UmcGFnZVBhdGg9cHJpdmF0ZS1uZXh0LWFwcC1kaXIlMkZhcHAtZWRnZS1zc3IlMkZwYWdlLmpzJmFwcERpcj0lMkZ0bXAlMkZuZXh0LXN0YXRzRklBYUlHJTJGc3RhdHMtYXBwJTJGYXBwJmFwcFBhdGhzPSUyRmFwcC1lZGdlLXNzciUyRnBhZ2UmcGFnZUV4dGVuc2lvbnM9dHN4JnBhZ2VFeHRlbnNpb25zPXRzJnBhZ2VFeHRlbnNpb25zPWpzeCZwYWdlRXh0ZW5zaW9ucz1qcyZiYXNlUGF0aD0mYXNzZXRQcmVmaXg9Jm5leHRDb25maWdPdXRwdXQ9JmZseWluZ1NodXR0bGU9ZmFsc2UmcHJlZmVycmVkUmVnaW9uPSZtaWRkbGV3YXJlQ29uZmlnPWUzMCUzRCE=","sriEnabled":false,"middlewareConfig":"e30=","cacheHandlers":"{}"}!
       var _self___RSC_MANIFEST;
 
       const incrementalCacheHandler = null;
@@ -456,56 +456,56 @@
       /***/
     },
 
-    /***/ 9938: /***/ (
+    /***/ 6609: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 3080)
+        __webpack_require__.bind(__webpack_require__, 6831)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 8158)
+        __webpack_require__.bind(__webpack_require__, 8483)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 6025)
+        __webpack_require__.bind(__webpack_require__, 9469)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 4399)
+        __webpack_require__.bind(__webpack_require__, 8542)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 2908)
+        __webpack_require__.bind(__webpack_require__, 6692)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 880)
+        __webpack_require__.bind(__webpack_require__, 1810)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 8683)
+        __webpack_require__.bind(__webpack_require__, 7170)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 943)
+        __webpack_require__.bind(__webpack_require__, 1434)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 6186)
+        __webpack_require__.bind(__webpack_require__, 2143)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 3115)
+        __webpack_require__.bind(__webpack_require__, 4403)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 3906)
+        __webpack_require__.bind(__webpack_require__, 1634)
       );
       Promise.resolve(/* import() eager */).then(
-        __webpack_require__.bind(__webpack_require__, 6714)
+        __webpack_require__.bind(__webpack_require__, 5293)
       );
 
       /***/
     },
 
-    /***/ 4679: /***/ () => {
+    /***/ 6715: /***/ () => {
       /***/
     },
 
-    /***/ 4270: /***/ (
+    /***/ 8250: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -525,7 +525,7 @@
       /***/
     },
 
-    /***/ 8827: /***/ (
+    /***/ 4114: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -537,7 +537,7 @@
         /* harmony export */
       });
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
-        __webpack_require__(6090);
+        __webpack_require__(5783);
 
       function RootLayout({ children }) {
         return /*#__PURE__*/ (0,
@@ -556,7 +556,7 @@
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
-    /******/ __webpack_require__.O(0, [89, 985], () => __webpack_exec__(9355));
+    /******/ __webpack_require__.O(0, [81, 809], () => __webpack_exec__(2486));
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ (_ENTRIES = typeof _ENTRIES === "undefined" ? {} : _ENTRIES)[
       "middleware_app/app-edge-ssr/page"
Diff for middleware.js

Diff too large to display

Diff for edge-ssr.js

Diff too large to display

Diff for dynamic-HASH.js
@@ -1,7 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [2739],
   {
-    /***/ 559: /***/ (
+    /***/ 7848: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -9,7 +9,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/dynamic",
         function () {
-          return __webpack_require__(3073);
+          return __webpack_require__(1691);
         },
       ]);
       if (false) {
@@ -18,7 +18,7 @@
       /***/
     },
 
-    /***/ 1586: /***/ (module, exports, __webpack_require__) => {
+    /***/ 1756: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -51,7 +51,7 @@
         __webpack_require__(8966)
       );
       const _loadablesharedruntime = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(5739)
+        __webpack_require__(8970)
       );
       const isServerSide = "object" === "undefined";
       // Normalize loader to return the module as form { default: Component } for `React.lazy`.
@@ -152,7 +152,7 @@
       /***/
     },
 
-    /***/ 5372: /***/ (
+    /***/ 1203: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -179,7 +179,7 @@
       /***/
     },
 
-    /***/ 5739: /***/ (
+    /***/ 8970: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -221,7 +221,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       const _react = /*#__PURE__*/ _interop_require_default._(
         __webpack_require__(8966)
       );
-      const _loadablecontextsharedruntime = __webpack_require__(5372);
+      const _loadablecontextsharedruntime = __webpack_require__(1203);
       function resolve(obj) {
         return obj && obj.default ? obj.default : obj;
       }
@@ -456,7 +456,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       /***/
     },
 
-    /***/ 3073: /***/ (
+    /***/ 1691: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -471,7 +471,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(191);
       /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(35);
+        __webpack_require__(2093);
       /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_dynamic__WEBPACK_IMPORTED_MODULE_1__
@@ -480,12 +480,12 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       const DynamicHello = next_dynamic__WEBPACK_IMPORTED_MODULE_1___default()(
         () =>
           __webpack_require__
-            .e(/* import() */ 6554)
-            .then(__webpack_require__.bind(__webpack_require__, 6554))
+            .e(/* import() */ 6026)
+            .then(__webpack_require__.bind(__webpack_require__, 6026))
             .then((mod) => mod.Hello),
         {
           loadableGenerated: {
-            webpack: () => [/*require.resolve*/ 6554],
+            webpack: () => [/*require.resolve*/ 6026],
           },
         }
       );
@@ -512,8 +512,12 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       /***/
     },
 
-    /***/ 35: /***/ (module, __unused_webpack_exports, __webpack_require__) => {
-      module.exports = __webpack_require__(1586);
+    /***/ 2093: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(1756);
 
       /***/
     },
@@ -523,7 +527,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [2888, 9774, 179], () =>
-      __webpack_exec__(559)
+      __webpack_exec__(7848)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for image-HASH.js
@@ -1,7 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [8358],
   {
-    /***/ 9320: /***/ (
+    /***/ 1654: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -9,7 +9,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/image",
         function () {
-          return __webpack_require__(452);
+          return __webpack_require__(1251);
         },
       ]);
       if (false) {
@@ -18,7 +18,7 @@
       /***/
     },
 
-    /***/ 7876: /***/ (module, exports, __webpack_require__) => {
+    /***/ 9966: /***/ (module, exports, __webpack_require__) => {
       "use strict";
       /* __next_internal_client_entry_do_not_use__  cjs */
       Object.defineProperty(exports, "__esModule", {
@@ -40,17 +40,17 @@
         __webpack_require__(7811)
       );
       const _head = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(9825)
+        __webpack_require__(9953)
       );
-      const _getimgprops = __webpack_require__(5306);
-      const _imageconfig = __webpack_require__(2395);
-      const _imageconfigcontextsharedruntime = __webpack_require__(5181);
-      const _warnonce = __webpack_require__(1614);
-      const _routercontextsharedruntime = __webpack_require__(450);
+      const _getimgprops = __webpack_require__(839);
+      const _imageconfig = __webpack_require__(3799);
+      const _imageconfigcontextsharedruntime = __webpack_require__(622);
+      const _warnonce = __webpack_require__(7864);
+      const _routercontextsharedruntime = __webpack_require__(6498);
       const _imageloader = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(4342)
+        __webpack_require__(1648)
       );
-      const _usemergedref = __webpack_require__(3680);
+      const _usemergedref = __webpack_require__(8436);
       // This is replaced by webpack define plugin
       const configEnv = {
         deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
@@ -371,7 +371,7 @@
       /***/
     },
 
-    /***/ 3680: /***/ (module, exports, __webpack_require__) => {
+    /***/ 8436: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -432,7 +432,7 @@
       /***/
     },
 
-    /***/ 5306: /***/ (
+    /***/ 839: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -448,9 +448,9 @@
           return getImgProps;
         },
       });
-      const _warnonce = __webpack_require__(1614);
-      const _imageblursvg = __webpack_require__(494);
-      const _imageconfig = __webpack_require__(2395);
+      const _warnonce = __webpack_require__(7864);
+      const _imageblursvg = __webpack_require__(1583);
+      const _imageconfig = __webpack_require__(3799);
       const VALID_LOADING_VALUES =
         /* unused pure expression or super */ null && [
           "lazy",
@@ -824,7 +824,7 @@
       /***/
     },
 
-    /***/ 494: /***/ (__unused_webpack_module, exports) => {
+    /***/ 1583: /***/ (__unused_webpack_module, exports) => {
       "use strict";
       /**
        * A shared function, used on both client and server, to generate a SVG blur placeholder.
@@ -879,7 +879,7 @@
       /***/
     },
 
-    /***/ 4039: /***/ (
+    /***/ 973: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -906,10 +906,10 @@
         },
       });
       const _interop_require_default = __webpack_require__(9608);
-      const _getimgprops = __webpack_require__(5306);
-      const _imagecomponent = __webpack_require__(7876);
+      const _getimgprops = __webpack_require__(839);
+      const _imagecomponent = __webpack_require__(9966);
       const _imageloader = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(4342)
+        __webpack_require__(1648)
       );
       function getImageProps(imgProps) {
         const { props } = (0, _getimgprops.getImgProps)(imgProps, {
@@ -941,7 +941,7 @@
       /***/
     },
 
-    /***/ 4342: /***/ (__unused_webpack_module, exports) => {
+    /***/ 1648: /***/ (__unused_webpack_module, exports) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -976,7 +976,7 @@
       /***/
     },
 
-    /***/ 452: /***/ (
+    /***/ 1251: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -993,8 +993,8 @@
 
       // EXTERNAL MODULE: ./node_modules/.pnpm/[email protected]/node_modules/react/jsx-runtime.js
       var jsx_runtime = __webpack_require__(191);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_lmdvfmjq4cjj6zeyg7ucgwxtgm/node_modules/next/image.js
-      var next_image = __webpack_require__(1047);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0-rc-65a56d0e-20241020_re_mrxwdyewdpyfozpybp6e5l6che/node_modules/next/image.js
+      var next_image = __webpack_require__(382);
       var image_default = /*#__PURE__*/ __webpack_require__.n(next_image); // CONCATENATED MODULE: ./pages/nextjs.png
       /* harmony default export */ const nextjs = {
         src: "/_next/static/media/nextjs.cae0b805.png",
@@ -1024,12 +1024,12 @@
       /***/
     },
 
-    /***/ 1047: /***/ (
+    /***/ 382: /***/ (
       module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(4039);
+      module.exports = __webpack_require__(973);
 
       /***/
     },
@@ -1039,7 +1039,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [2888, 9774, 179], () =>
-      __webpack_exec__(9320)
+      __webpack_exec__(1654)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for 7758-HASH.js

Diff too large to display

Commit: f819397

@kdy1 kdy1 marked this pull request as draft October 16, 2024 02:37
@kdy1 kdy1 marked this pull request as ready for review October 16, 2024 02:42
@kdy1 kdy1 changed the title Fix EcmascriptModuleFacadeModule::ident() fix(turbopack): Fix EcmascriptModuleFacadeModule::ident() Oct 16, 2024
Base automatically changed from kdy1/ts-fragment-ident to canary October 17, 2024 07:12
@kdy1 kdy1 force-pushed the kdy1/ts-facade-module-ident branch from 1764558 to 2d47dac Compare October 17, 2024 07:12
@ijjk
Copy link
Member

ijjk commented Oct 17, 2024

Failing test suites

Commit: f819397

pnpm test-start-turbo test/e2e/app-dir/actions/app-action-form-state.test.ts (turbopack)

  • app-dir action useActionState > should support submitting form state with JS
  • app-dir action useActionState > should support submitting form state without JS
  • app-dir action useActionState > should support hydrating the app from progressively enhanced form request
  • app-dir action useActionState > should send the action to the provided permalink with form state when JS disabled
Expand output

● app-dir action useActionState › should support submitting form state with JS

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action useActionState › should support submitting form state without JS

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action useActionState › should support hydrating the app from progressively enhanced form request

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action useActionState › should send the action to the provided permalink with form state when JS disabled

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

Read more about building and testing Next.js in contributing.md.

pnpm test-start-turbo test/e2e/app-dir/app-basepath/index.test.ts (turbopack)

  • app dir - basepath > should successfully hard navigate from pages -> app
  • app dir - basepath > should support basePath
  • app dir - basepath > should support Link with basePath prefixed
  • app dir - basepath > should prefix metadata og image with basePath
  • app dir - basepath > should prefix redirect() with basePath
  • app dir - basepath > should render usePathname without the basePath
  • app dir - basepath > should handle redirect in dynamic in suspense boundary routes with basePath
  • app dir - basepath > should only make a single RSC call to the current page (/base/refresh)
  • app dir - basepath > should only make a single RSC call to the current page (/base/refresh?foo=bar)
  • app dir - basepath > should properly stream an internal server action redirect() with a relative URL
  • app dir - basepath > should properly stream an internal server action redirect() with a absolute URL
  • app dir - basepath > should redirect externally when encountering absolute URLs on the same host outside the basePath
Expand output

● app dir - basepath › should successfully hard navigate from pages -> app

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should support basePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should support Link with basePath prefixed

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should prefix metadata og image with basePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should prefix redirect() with basePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should render usePathname without the basePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should handle redirect in dynamic in suspense boundary routes with basePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should only make a single RSC call to the current page (/base/refresh)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should only make a single RSC call to the current page (/base/refresh?foo=bar)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should properly stream an internal server action redirect() with a relative URL

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should properly stream an internal server action redirect() with a absolute URL

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app dir - basepath › should redirect externally when encountering absolute URLs on the same host outside the basePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

Read more about building and testing Next.js in contributing.md.

pnpm test-start-turbo test/e2e/app-dir/actions/app-action-progressive-enhancement.test.ts (turbopack)

  • app-dir action progressive enhancement > should support formData and redirect without JS
  • app-dir action progressive enhancement > should support actions from client without JS
Expand output

● app-dir action progressive enhancement › should support formData and redirect without JS

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action progressive enhancement › should support actions from client without JS

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

Read more about building and testing Next.js in contributing.md.

pnpm test test/integration/app-dynamic-error/test/index.test.ts (turbopack)

  • app-dynamic-error > production mode > throws an error when prerendering a page with config dynamic error
Expand output

● app-dynamic-error › production mode › throws an error when prerendering a page with config dynamic error

expect(received).toContain(expected) // indexOf

Expected substring: "Error occurred prerendering page \"/dynamic-error\""
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
[Error: Failed to write app endpoint /_not-found/page·
Caused by:
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/server/response-cache/index.js [app-rsc] (ecmascript)'
- could not find part id for module part Export(\"IncrementalCacheKind\") in {ModuleEvaluation: 0, Export(\"default\"): 1, Exports: 14}·
Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <AppEndpoint as Endpoint>::write_to_disk failed
- Failed to write app endpoint /_not-found/page
- Execution of AppEndpoint::output failed
- Execution of client_reference_graph failed
- Execution of primary_referenced_modules failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/server/response-cache/index.js [app-rsc] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export(\"IncrementalCacheKind\") in {ModuleEvaluation: 0, Export(\"default\"): 1, Exports: 14}···
  Module dump:
  # Module #0:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 12
  };
  \"module evaluation\";············
  # Module #1:
  import { a as ResponseCache } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -13
  };
  export { ResponseCache as default };············
  # Module #2:
  import './types';············
  # Module #3:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 2
  };
  import { CachedRouteKind } from './types';
  export { CachedRouteKind as b };············
  # Module #4:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 2
  };
  import '../../lib/batcher';············
  # Module #5:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 4
  };
  import { Batcher } from '../../lib/batcher';
  export { Batcher as c };············
  # Module #6:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 4
  };
  import '../../lib/scheduler';············
  # Module #7:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 6
  };
  import { scheduleOnNextTick } from '../../lib/scheduler';
  export { scheduleOnNextTick as d };············
  # Module #8:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 6
  };
  import './utils';············
  # Module #9:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 8
  };
  import { fromResponseCacheEntry } from './utils';
  export { fromResponseCacheEntry as e };············
  # Module #10:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 8
  };
  import { routeKindToIncrementalCacheKind } from './utils';
  export { routeKindToIncrementalCacheKind as f };············
  # Module #11:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 8
  };
  import { toResponseCacheEntry } from './utils';
  export { toResponseCacheEntry as g };············
  # Module #12:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 8
  };
  import './types';············
  # Module #13:
  import { g as toResponseCacheEntry } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -11
  };
  import { c as Batcher } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -5
  };
  import { d as scheduleOnNextTick } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -7
  };
  import { f as routeKindToIncrementalCacheKind } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -10
  };
  import { b as CachedRouteKind } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -3
  };
  import { e as fromResponseCacheEntry } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: -9
  };
  class ResponseCache {
      constructor(minimalMode){
          this.batcher = Batcher.create({
              cacheKeyFn: ({ key, isOnDemandRevalidate })=>`${key}-${isOnDemandRevalidate ? '1' : '0'}`,
              schedulerFn: scheduleOnNextTick
          });
          const minimalModeKey = 'minimalMode';
          this[minimalModeKey] = minimalMode;
      }
      async get(key, responseGenerator, context) {
          if (!key) {
              return responseGenerator({
                  hasResolved: false,
                  previousCacheEntry: null
              });
          }
          const { incrementalCache, isOnDemandRevalidate = false, isFallback = false, isRoutePPREnabled = false } = context;
          const response = await this.batcher.batch({
              key,
              isOnDemandRevalidate
          }, async (cacheKey, resolve)=>{
              var _this_previousCacheItem;
              if (this.minimalMode && ((_this_previousCacheItem = this.previousCacheItem) == null ? void 0 : _this_previousCacheItem.key) === cacheKey && this.previousCacheItem.expiresAt > Date.now()) {
                  return this.previousCacheItem.entry;
              }
              const kind = routeKindToIncrementalCacheKind(context.routeKind);
              let resolved = false;
              let cachedResponse = null;
              try {
                  cachedResponse = !this.minimalMode ? await incrementalCache.get(key, {
                      kind,
                      isRoutePPREnabled: context.isRoutePPREnabled,
                      isFallback
                  }) : null;
                  if (cachedResponse && !isOnDemandRevalidate) {
                      var _cachedResponse_value;
                      if (((_cachedResponse_value = cachedResponse.value) == null ? void 0 : _cachedResponse_value.kind) === CachedRouteKind.FETCH) {
                          throw new Error(`invariant: unexpected cachedResponse of kind fetch in response cache`);
                      }
                      resolve({
                          ...cachedResponse,
                          revalidate: cachedResponse.curRevalidate
                      });
                      resolved = true;
                      if (!cachedResponse.isStale || context.isPrefetch) {
                          return null;
                      }
                  }
                  const cacheEntry = await responseGenerator({
                      hasResolved: resolved,
                      previousCacheEntry: cachedResponse,
                      isRevalidating: true
                  });
                  if (!cacheEntry) {
                      if (this.minimalMode) this.previousCacheItem = undefined;
                      return null;
                  }
                  const resolveValue = await fromResponseCacheEntry({
                      ...cacheEntry,
                      isMiss: !cachedResponse
                  });
                  if (!resolveValue) {
                      if (this.minimalMode) this.previousCacheItem = undefined;
                      return null;
                  }
                  if (!isOnDemandRevalidate && !resolved) {
                      resolve(resolveValue);
                      resolved = true;
                  }
                  if (typeof resolveValue.revalidate !== 'undefined') {
                      if (this.minimalMode) {
                          this.previousCacheItem = {
                              key: cacheKey,
                              entry: resolveValue,
                              expiresAt: Date.now() + 1000
                          };
                      } else {
                          await incrementalCache.set(key, resolveValue.value, {
                              revalidate: resolveValue.revalidate,
                              isRoutePPREnabled,
                              isFallback
                          });
                      }
                  }
                  return resolveValue;
              } catch (err) {
                  if (cachedResponse) {
                      await incrementalCache.set(key, cachedResponse.value, {
                          revalidate: Math.min(Math.max(cachedResponse.revalidate || 3, 3), 30),
                          isRoutePPREnabled,
                          isFallback
                      });
                  }
                  if (resolved) {
                      console.error(err);
                      return null;
                  }
                  throw err;
              }
          });
          return toResponseCacheEntry(response);
      }
  }
  export { ResponseCache as a };············
  # Module #14:
  export { default } from \"__TURBOPACK_PART__\" with {
      __turbopack_part__: \"export default\"
  };
  export * from './types';·········
  ] {
  name: 'TurbopackInternalError'
}
"

  11 |           stdout: true,
  12 |         })
> 13 |         expect(stderr).toContain(
     |                        ^
  14 |           'Error occurred prerendering page "/dynamic-error"'
  15 |         )
  16 |         expect(code).toBe(1)

  at Object.toContain (integration/app-dynamic-error/test/index.test.ts:13:24)

Read more about building and testing Next.js in contributing.md.

pnpm test-start-turbo test/e2e/app-dir/actions/app-action.test.ts (turbopack)

  • app-dir action handling > should handle action correctly with middleware rewrite
  • app-dir action handling > should handle basic actions correctly
  • app-dir action handling > should report errors with bad inputs correctly
  • app-dir action handling > should propagate errors from a text/plain response to an error boundary
  • app-dir action handling > should trigger an error boundary for action responses with an invalid content-type
  • app-dir action handling > should support headers and cookies
  • app-dir action handling > should push new route when redirecting
  • app-dir action handling > should replace current route when redirecting with type set to replace
  • app-dir action handling > should support headers in client imported actions
  • app-dir action handling > should not log errors for non-action form POSTs
  • app-dir action handling > should support setting cookies in route handlers with the correct overrides
  • app-dir action handling > should support formData and redirect
  • app-dir action handling > should support .bind
  • app-dir action handling > should support chained .bind
  • app-dir action handling > should support notFound (javascript disabled)
  • app-dir action handling > should support notFound
  • app-dir action handling > should support uploading files
  • app-dir action handling > should support hoc auth wrappers
  • app-dir action handling > should support importing actions in client components
  • app-dir action handling > should support importing the same action module instance in both server and action layers
  • app-dir action handling > should not block navigation events while a server action is in flight
  • app-dir action handling > should not block router.back() while a server action is in flight
  • app-dir action handling > should trigger a refresh for a server action that gets discarded due to a navigation
  • app-dir action handling > should trigger a refresh for a server action that also dispatches a navigation event
  • app-dir action handling > should support next/dynamic with ssr: false
  • app-dir action handling > should support next/dynamic with ssr: false (edge)
  • app-dir action handling > should only submit action once when resubmitting an action after navigation
  • app-dir action handling > should handle actions executed in quick succession
  • app-dir action handling > should reset the form state when the action redirects to a page that contains the same form
  • app-dir action handling > should invalidate the client router cache if the redirect action triggers a revalidation
  • app-dir action handling > should reset the form state when the action redirects to itself
  • app-dir action handling > should 404 when POSTing an invalid server action
  • app-dir action handling > should log a warning when a server action is not found but an id is provided
  • app-dir action handling > should be possible to catch network errors
  • app-dir action handling > should be possible to catch regular errors
  • app-dir action handling > should forward action request to a worker that contains the action handler (node)
  • app-dir action handling > should forward action request to a worker that contains the action handler (edge)
  • app-dir action handling > should not error when a forwarded action triggers a redirect (node)
  • app-dir action handling > should not error when a forwarded action triggers a redirect (edge)
  • app-dir action handling > should work with interception routes
  • app-dir action handling > Edge SSR > should handle basic actions correctly
  • app-dir action handling > Edge SSR > should return error response for hoc auth wrappers in edge runtime
  • app-dir action handling > Edge SSR > should handle calls to redirect() with a relative URL in a single pass
  • app-dir action handling > Edge SSR > should handle calls to redirect() with a absolute URL in a single pass
  • app-dir action handling > Edge SSR > should handle calls to redirect() with external URLs
  • app-dir action handling > Edge SSR > should allow cookie and header async storages
  • app-dir action handling > Edge SSR > should handle unicode search params
  • app-dir action handling > caching disabled by default > should use no-store as default for server action
  • app-dir action handling > caching disabled by default > should not override force-cache in server action
  • app-dir action handling > caching disabled by default > should not override revalidate in server action
  • app-dir action handling > encryption > should send encrypted values from the closed over closure
  • app-dir action handling > fetch actions > should handle a fetch action initiated from a static page
  • app-dir action handling > fetch actions > should handle calls to redirect() with a relative URL in a single pass
  • app-dir action handling > fetch actions > should handle calls to redirect() with a absolute URL in a single pass
  • app-dir action handling > fetch actions > should handle calls to redirect() with external URLs
  • app-dir action handling > fetch actions > should handle redirects to routes that provide an invalid RSC response
  • app-dir action handling > fetch actions > should handle revalidatePath
  • app-dir action handling > fetch actions > should handle revalidateTag
  • app-dir action handling > fetch actions > should store revalidation data in the prefetch cache
  • app-dir action handling > fetch actions > should revalidate when cookies.set is called
  • app-dir action handling > fetch actions > should invalidate client cache on other routes when cookies.set is called
  • app-dir action handling > fetch actions > should revalidate when cookies.set is called in a client action
  • app-dir action handling > fetch actions > should invalidate client cache when tag is revalidated
  • app-dir action handling > fetch actions > should invalidate client cache when path is revalidated
  • app-dir action handling > redirects > redirects properly when server action handler uses redirect
  • app-dir action handling > redirects > redirects properly when server action handler uses permanentRedirect
  • app-dir action handling > redirects > displays searchParams correctly when redirecting with SearchParams
  • app-dir action handling > redirects > merges cookies correctly when redirecting
  • app-dir action handling > redirects > should not forward next-action header to a redirected RSC request
  • app-dir action handling > redirects > redirects properly when server action handler redirects with a 307 status code
  • app-dir action handling > redirects > redirects properly when server action handler redirects with a 308 status code
  • app-dir action handling > server actions render client components > server component imported action > should support importing client components from actions
Expand output

● app-dir action handling › should handle action correctly with middleware rewrite

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should handle basic actions correctly

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should report errors with bad inputs correctly

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should propagate errors from a text/plain response to an error boundary

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should trigger an error boundary for action responses with an invalid content-type

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support headers and cookies

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should push new route when redirecting

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should replace current route when redirecting with type set to replace

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support headers in client imported actions

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should not log errors for non-action form POSTs

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support setting cookies in route handlers with the correct overrides

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support formData and redirect

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support .bind

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support chained .bind

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support notFound (javascript disabled)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support notFound

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support uploading files

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support hoc auth wrappers

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support importing actions in client components

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support importing the same action module instance in both server and action layers

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should not block navigation events while a server action is in flight

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should not block router.back() while a server action is in flight

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should trigger a refresh for a server action that gets discarded due to a navigation

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should trigger a refresh for a server action that also dispatches a navigation event

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support next/dynamic with ssr: false

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should support next/dynamic with ssr: false (edge)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should only submit action once when resubmitting an action after navigation

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should handle actions executed in quick succession

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should reset the form state when the action redirects to a page that contains the same form

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should invalidate the client router cache if the redirect action triggers a revalidation

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should reset the form state when the action redirects to itself

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should 404 when POSTing an invalid server action

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should log a warning when a server action is not found but an id is provided

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should be possible to catch network errors

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should be possible to catch regular errors

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should forward action request to a worker that contains the action handler (node)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should forward action request to a worker that contains the action handler (edge)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should not error when a forwarded action triggers a redirect (node)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should not error when a forwarded action triggers a redirect (edge)

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should not expose action content in sourcemaps

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should handle basic actions correctly

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should return error response for hoc auth wrappers in edge runtime

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should handle calls to redirect() with a relative URL in a single pass

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should handle calls to redirect() with a absolute URL in a single pass

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should handle calls to redirect() with external URLs

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should allow cookie and header async storages

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › Edge SSR › should handle unicode search params

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle a fetch action initiated from a static page

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle calls to redirect() with a relative URL in a single pass

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle calls to redirect() with a absolute URL in a single pass

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle calls to redirect() with external URLs

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle redirects to routes that provide an invalid RSC response

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle revalidatePath

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle revalidateTag

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should handle revalidateTag + redirect

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should store revalidation data in the prefetch cache

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should revalidate when cookies.set is called

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should invalidate client cache on other routes when cookies.set is called

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should revalidate when cookies.set is called in a client action

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should invalidate client cache when tag is revalidated

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › fetch actions › should invalidate client cache when path is revalidated

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should work with interception routes

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › encryption › should send encrypted values from the closed over closure

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › redirects properly when server action handler uses redirect

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › redirects properly when server action handler uses permanentRedirect

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › displays searchParams correctly when redirecting with SearchParams

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › merges cookies correctly when redirecting

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › should not forward next-action header to a redirected RSC request

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › redirects properly when server action handler redirects with a 307 status code

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › redirects › redirects properly when server action handler redirects with a 308 status code

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › server actions render client components › server component imported action › should support importing client components from actions

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › server actions render client components › client component imported action › should support importing client components from actions

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › caching disabled by default › should use no-store as default for server action

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › caching disabled by default › should not override force-cache in server action

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › caching disabled by default › should not override revalidate in server action

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

Read more about building and testing Next.js in contributing.md.

pnpm test-start-turbo test/e2e/app-dir/actions-navigation/index.test.ts (turbopack)

  • app-dir action handling > should handle actions correctly after navigation / redirection events
  • app-dir action handling > should handle actions correctly after following a relative link
Expand output

● app-dir action handling › should handle actions correctly after navigation / redirection events

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

● app-dir action handling › should handle actions correctly after following a relative link

next build failed with code/signal 1

   98 |           if (code || signal)
   99 |             reject(
> 100 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  101 |             )
  102 |           else resolve()
  103 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:100:15)

Read more about building and testing Next.js in contributing.md.

pnpm test test/integration/edge-runtime-streaming-error/test/index.test.ts (turbopack)

  • production mode > logs the error correctly
Expand output

● production mode › logs the error correctly

FetchError: request to http://localhost:39589/api/test failed, reason: connect ECONNREFUSED 127.0.0.1:39589

  at ClientRequest.<anonymous> (../node_modules/.pnpm/[email protected][email protected]/node_modules/node-fetch/lib/index.js:1491:11)

Read more about building and testing Next.js in contributing.md.

pnpm test test/integration/middleware-src/test/index.test.js (turbopack)

  • Middleware in src/ and / folders > production mode > should warn about middleware on export
  • Middleware in src/ folder > production mode > should warn about middleware on export
Expand output

● Middleware in src/ folder › production mode › should warn about middleware on export

expect(received).toContain(expected) // indexOf

Expected substring: "Statically exporting a Next.js application via `next export` disables API routes and middleware."
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'·
Caused by:
- could not find part id for module part Export(\"NextResponse\") in {ModuleEvaluation: 0, Exports: 2}·
Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export(\"NextResponse\") in {ModuleEvaluation: 0, Exports: 2}···
  Module dump:
  # Module #0:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 1
  };
  \"module evaluation\";············
  # Module #1:
  import '../server/web/exports/index';············
  # Module #2:
  export * from '../server/web/exports/index';·········
  ] {
  name: 'TurbopackInternalError'
}
  ▲ Next.js 15.0.0-canary.202 (turbo)·
   Checking validity of types ...
   Creating an optimized production build ...
"

  122 |
  123 |       it('should warn about middleware on export', async () => {
> 124 |         expect(exportOutput).toContain(
      |                              ^
  125 |           'Statically exporting a Next.js application via `next export` disables API routes and middleware.'
  126 |         )
  127 |       })

  at Object.toContain (integration/middleware-src/test/index.test.js:124:30)

● Middleware in src/ and / folders › production mode › should warn about middleware on export

expect(received).toContain(expected) // indexOf

Expected substring: "Statically exporting a Next.js application via `next export` disables API routes and middleware."
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'·
Caused by:
- could not find part id for module part Export(\"NextResponse\") in {ModuleEvaluation: 0, Exports: 2}·
Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export(\"NextResponse\") in {ModuleEvaluation: 0, Exports: 2}···
  Module dump:
  # Module #0:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 1
  };
  \"module evaluation\";············
  # Module #1:
  import '../server/web/exports/index';············
  # Module #2:
  export * from '../server/web/exports/index';·········
  ] {
  name: 'TurbopackInternalError'
}
  ▲ Next.js 15.0.0-canary.202 (turbo)·
   Checking validity of types ...
   Creating an optimized production build ...
"

  122 |
  123 |       it('should warn about middleware on export', async () => {
> 124 |         expect(exportOutput).toContain(
      |                              ^
  125 |           'Statically exporting a Next.js application via `next export` disables API routes and middleware.'
  126 |         )
  127 |       })

  at Object.toContain (integration/middleware-src/test/index.test.js:124:30)

Read more about building and testing Next.js in contributing.md.

pnpm test test/integration/dynamic-routing/test/middleware.test.js (turbopack)

  • Dynamic Routing > production mode > should have correct cache entries on prefetch
  • Dynamic Routing > production mode > should support long URLs for dynamic routes
  • Dynamic Routing > production mode > should handle only query on dynamic route
  • Dynamic Routing > production mode > should handle only hash on dynamic route
  • Dynamic Routing > production mode > should navigate with hash to dynamic route with link
  • Dynamic Routing > production mode > should navigate with hash to dynamic route with router
  • Dynamic Routing > production mode > should not have any query values when not defined
  • Dynamic Routing > production mode > should render normal route
  • Dynamic Routing > production mode > should render another normal route
  • Dynamic Routing > production mode > should render dynamic page
  • Dynamic Routing > production mode > should prioritize a non-dynamic page
  • Dynamic Routing > production mode > should render nested dynamic page
  • Dynamic Routing > production mode > should render optional dynamic page
  • Dynamic Routing > production mode > should render nested optional dynamic page
  • Dynamic Routing > production mode > should not error when requesting dynamic page with /api
  • Dynamic Routing > production mode > should render dynamic route with query
  • Dynamic Routing > production mode > should navigate to a dynamic page successfully
  • Dynamic Routing > production mode > should navigate to a dynamic page with href with differing query and as correctly
  • Dynamic Routing > production mode > should navigate to a dynamic page successfully no as
  • Dynamic Routing > production mode > should navigate to a dynamic page successfully interpolated
  • Dynamic Routing > production mode > should navigate to a dynamic page successfully interpolated with additional query values
  • Dynamic Routing > production mode > should allow calling Router.push on mount successfully
  • Dynamic Routing > production mode > should navigate optional dynamic page
  • Dynamic Routing > production mode > should navigate optional dynamic page with value
  • Dynamic Routing > production mode > should navigate to a nested dynamic page successfully
  • Dynamic Routing > production mode > should navigate to a nested dynamic page successfully no as
  • Dynamic Routing > production mode > should navigate to a nested dynamic page successfully interpolated
  • Dynamic Routing > production mode > should pass params in getInitialProps during SSR
  • Dynamic Routing > production mode > should pass params in getInitialProps during client navigation
  • Dynamic Routing > production mode > [catch all] should not match root on SSR
  • Dynamic Routing > production mode > [catch all] should pass param in getInitialProps during SSR
  • Dynamic Routing > production mode > [catch all] should pass params in getInitialProps during SSR
  • Dynamic Routing > production mode > [catch all] should strip trailing slash
  • Dynamic Routing > production mode > [catch all] should not decode slashes (start)
  • Dynamic Routing > production mode > [catch all] should not decode slashes (end)
  • Dynamic Routing > production mode > [catch all] should not decode slashes (middle)
  • Dynamic Routing > production mode > [catch-all] should pass params in getInitialProps during client navigation (single)
  • Dynamic Routing > production mode > [catch-all] should pass params in getInitialProps during client navigation (multi)
  • Dynamic Routing > production mode > [catch-all] should pass params in getInitialProps during client navigation (encoded)
  • Dynamic Routing > production mode > [catch-all] shouldn't fail on colon followed by double digits in the path
  • Dynamic Routing > production mode > [ssg: catch all] should pass param in getStaticProps during SSR
  • Dynamic Routing > production mode > [ssg: catch all] should pass params in getStaticProps during SSR
  • Dynamic Routing > production mode > [nested ssg: catch all] should pass param in getStaticProps during SSR
  • Dynamic Routing > production mode > [nested ssg: catch all] should pass params in getStaticProps during SSR
  • Dynamic Routing > production mode > [predefined ssg: catch all] should pass param in getStaticProps during SSR
  • Dynamic Routing > production mode > [predefined ssg: catch all] should pass params in getStaticProps during SSR
  • Dynamic Routing > production mode > [predefined ssg: prerendered catch all] should pass param in getStaticProps during SSR
  • Dynamic Routing > production mode > [predefined ssg: prerendered catch all] should pass params in getStaticProps during SSR
  • Dynamic Routing > production mode > [ssg: catch-all] should pass params in getStaticProps during client navigation (single)
  • Dynamic Routing > production mode > [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)
  • Dynamic Routing > production mode > [ssg: catch-all] should pass params in getStaticProps during client navigation (multi)
  • Dynamic Routing > production mode > [ssg: catch-all] should pass params in getStaticProps during client navigation (multi) no as
  • Dynamic Routing > production mode > [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)
  • Dynamic Routing > production mode > [nested ssg: catch-all] should pass params in getStaticProps during client navigation (single)
  • Dynamic Routing > production mode > [nested ssg: catch-all] should pass params in getStaticProps during client navigation (multi)
  • Dynamic Routing > production mode > should update dynamic values on mount
  • Dynamic Routing > production mode > should not have placeholder query values for SSS
  • Dynamic Routing > production mode > should update with a hash in the URL
  • Dynamic Routing > production mode > should scroll to a hash on mount
  • Dynamic Routing > production mode > should scroll to a hash on client-side navigation
  • Dynamic Routing > production mode > should prioritize public files over dynamic route
  • Dynamic Routing > production mode > should serve file with space from public folder
  • Dynamic Routing > production mode > should serve file with plus from public folder
  • Dynamic Routing > production mode > should serve file from public folder encoded
  • Dynamic Routing > production mode > should serve file with %20 from public folder
  • Dynamic Routing > production mode > should serve file with space from static folder
  • Dynamic Routing > production mode > should serve file with plus from static folder
  • Dynamic Routing > production mode > should serve file from static folder encoded
  • Dynamic Routing > production mode > should serve file with %20 from static folder
  • Dynamic Routing > production mode > should respond with bad request with invalid encoding
  • Dynamic Routing > production mode > should not preload buildManifest for non-auto export dynamic pages
  • Dynamic Routing > production mode > should output a routes-manifest correctly
  • Dynamic Routing > production mode > should output a pages-manifest correctly
Expand output

● Dynamic Routing › production mode › should have correct cache entries on prefetch

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should support long URLs for dynamic routes

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should handle only query on dynamic route

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should handle only hash on dynamic route

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate with hash to dynamic route with link

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate with hash to dynamic route with router

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should not have any query values when not defined

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render normal route

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render another normal route

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render dynamic page

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should prioritize a non-dynamic page

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render nested dynamic page

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render optional dynamic page

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render nested optional dynamic page

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should not error when requesting dynamic page with /api

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should render dynamic route with query

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a dynamic page successfully

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a dynamic page with href with differing query and as correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a dynamic page successfully no as

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a dynamic page successfully interpolated

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a dynamic page successfully interpolated with additional query values

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should allow calling Router.push on mount successfully

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate optional dynamic page

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate optional dynamic page with value

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a nested dynamic page successfully

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a nested dynamic page successfully no as

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should navigate to a nested dynamic page successfully interpolated

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should pass params in getInitialProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should pass params in getInitialProps during client navigation

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should not match root on SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should pass param in getInitialProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should pass params in getInitialProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should strip trailing slash

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should not decode slashes (start)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should not decode slashes (end)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch all] should not decode slashes (middle)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch-all] should pass params in getInitialProps during client navigation (single)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch-all] should pass params in getInitialProps during client navigation (multi)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch-all] should pass params in getInitialProps during client navigation (encoded)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [catch-all] shouldn't fail on colon followed by double digits in the path

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch all] should pass param in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch all] should pass params in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [nested ssg: catch all] should pass param in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [nested ssg: catch all] should pass params in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [predefined ssg: catch all] should pass param in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [predefined ssg: catch all] should pass params in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [predefined ssg: prerendered catch all] should pass param in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [predefined ssg: prerendered catch all] should pass params in getStaticProps during SSR

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (single)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (multi)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (multi) no as

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [nested ssg: catch-all] should pass params in getStaticProps during client navigation (single)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › [nested ssg: catch-all] should pass params in getStaticProps during client navigation (multi)

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should update dynamic values on mount

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should not have placeholder query values for SSS

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should update with a hash in the URL

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should scroll to a hash on mount

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should scroll to a hash on client-side navigation

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should prioritize public files over dynamic route

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file with space from public folder

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file with plus from public folder

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file from public folder encoded

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file with %20 from public folder

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file with space from static folder

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file with plus from static folder

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file from static folder encoded

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should serve file with %20 from static folder

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should respond with bad request with invalid encoding

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should not preload buildManifest for non-auto export dynamic pages

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should output a routes-manifest correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

● Dynamic Routing › production mode › should output a pages-manifest correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
  ▲ Next.js 15.0.0-canary.202 (turbo)

   Checking validity of types ...
   Creating an optimized production build ...

> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'

Caused by:
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}

Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export("NextResponse") in {ModuleEvaluation: 0, Exports: 2}
  
  Module dump:
  # Module #0:
  import "__TURBOPACK_PART__" with {
      __turbopack_part__: 1
  };
  "module evaluation";
  
  
  
  
  # Module #1:
  import '../server/web/exports/index';
  
  
  
  
  # Module #2:
  export * from '../server/web/exports/index';
  
  
  
  ] {
  name: 'TurbopackInternalError'
}

  308 |       ) {
  309 |         return reject(
> 310 |           new Error(
      |           ^
  311 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  312 |           )
  313 |         )

  at ChildProcess.<anonymous> (lib/next-test-utils.ts:310:11)

Read more about building and testing Next.js in contributing.md.

pnpm test test/integration/edge-runtime-configurable-guards/test/index.test.js (turbopack)

  • Edge runtime configurable guards > Edge API using lib with unallowed, used dynamic code > production mode > fails to build because of dynamic code evaluation
  • Edge runtime configurable guards > Middleware using lib with unallowed, used dynamic code > production mode > fails to build because of dynamic code evaluation
  • Edge runtime configurable guards > Multiple functions with different configurations > production mode > fails to build because of unallowed code
Expand output

● Edge runtime configurable guards › Multiple functions with different configurations › production mode › fails to build because of unallowed code

expect(received).toContain(expected) // indexOf

Expected substring: "Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime"
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
[Error: ENOENT: no such file or directory, open '/root/actions-runner/_work/next.js/next.js/test/integration/edge-runtime-configurable-guards/.next/server/middleware/middleware-manifest.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/root/actions-runner/_work/next.js/next.js/test/integration/edge-runtime-configurable-guards/.next/server/middleware/middleware-manifest.json'
}
"

  117 |             expect(output.stderr).toContain(`./pages/api/route.js`)
  118 |           }
> 119 |           expect(output.stderr).toContain(
      |                                 ^
  120 |             `Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime`
  121 |           )
  122 |           if (!process.env.TURBOPACK) {

  at Object.toContain (integration/edge-runtime-configurable-guards/test/index.test.js:119:33)

● Edge runtime configurable guards › Edge API using lib with unallowed, used dynamic code › production mode › fails to build because of dynamic code evaluation

expect(received).toContain(expected) // indexOf

Expected substring: "Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime"
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
[Error: failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'·
Caused by:
- could not find part id for module part Export(\"NextResponse\") in {ModuleEvaluation: 0, Exports: 2}·
Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <MiddlewareEndpoint as Endpoint>::write_to_disk failed
- Execution of MiddlewareEndpoint::output_assets failed
- Execution of evaluated_chunk_group_assets failed
- Execution of <BrowserChunkingContext as ChunkingContext>::evaluated_chunk_group failed
- Execution of graph_node_to_referenced_nodes failed
- Execution of <EsmAssetReference as ModuleReference>::resolve_reference failed
- Execution of is_export_missing failed
- Execution of <EcmascriptModulePartAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/packages/next/dist/esm/api/server.js [middleware] (ecmascript)'
- Execution of part_of_module failed
- could not find part id for module part Export(\"NextResponse\") in {ModuleEvaluation: 0, Exports: 2}···
  Module dump:
  # Module #0:
  import \"__TURBOPACK_PART__\" with {
      __turbopack_part__: 1
  };
  \"module evaluation\";············
  # Module #1:
  import '../server/web/exports/index';············
  # Module #2:
  export * from '../server/web/exports/index';·········
  ] {
  name: 'TurbopackInternalError'
}
"

  417 |             env: process.env.TURBOPACK ? {} : { NEXT_TELEMETRY_DEBUG: 1 },
  418 |           })
> 419 |           expect(output.stderr).toContain(
      |                                 ^
  420 |             `Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime`
  421 |           )
  422 |           if (!process.env.TURBOPACK) {

  at Object.toContain (integration/edge-runtime-configurable-guards/test/index.test.js:419:33)

● Edge runtime configurable guards › Middleware using lib with unallowed, used dynamic code › production mode › fails to build because of dynamic code evaluation

expect(received).toContain(expected) // indexOf

Expected substring: "Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime"
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
[Error: ENOENT: no such file or directory, open '/root/actions-runner/_work/next.js/next.js/test/integration/edge-runtime-configurable-guards/.next/server/middleware/middleware-manifest.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/root/actions-runner/_work/next.js/next.js/test/integration/edge-runtime-configurable-guards/.next/server/middleware/middleware-manifest.json'
}
"

  417 |             env: process.env.TURBOPACK ? {} : { NEXT_TELEMETRY_DEBUG: 1 },
  418 |           })
> 419 |           expect(output.stderr).toContain(
      |                                 ^
  420 |             `Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime`
  421 |           )
  422 |           if (!process.env.TURBOPACK) {

  at Object.toContain (integration/edge-runtime-configurable-guards/test/index.test.js:419:33)

Read more about building and testing Next.js in contributing.md.

@kdy1 kdy1 force-pushed the kdy1/ts-facade-module-ident branch 2 times, most recently from c4346ba to b3f74d6 Compare October 17, 2024 10:38
@kdy1 kdy1 changed the base branch from canary to kdy1/ts-fix-default-module October 17, 2024 10:38
@kdy1 kdy1 force-pushed the kdy1/ts-fix-default-module branch from efbab25 to 86e2b35 Compare October 17, 2024 11:02
@kdy1 kdy1 force-pushed the kdy1/ts-facade-module-ident branch from b3f74d6 to fc86862 Compare October 17, 2024 11:08
@kdy1 kdy1 changed the base branch from kdy1/ts-fix-default-module to kdy1/ts-opt-export-star October 17, 2024 11:09
@kdy1 kdy1 force-pushed the kdy1/ts-facade-module-ident branch from fc86862 to e103e64 Compare October 21, 2024 06:59
@kdy1 kdy1 force-pushed the kdy1/ts-facade-module-ident branch from e103e64 to f819397 Compare October 21, 2024 07:16
@kdy1 kdy1 changed the base branch from kdy1/ts-opt-export-star to canary October 21, 2024 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
created-by: Turbopack team PRs by the Turbopack team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants