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): Use correct SyntaxContext for __turbopack_esm__ #73544

Draft
wants to merge 10 commits into
base: canary
Choose a base branch
from

Conversation

kdy1
Copy link
Member

@kdy1 kdy1 commented Dec 5, 2024

@kdy1 kdy1 self-assigned this Dec 5, 2024
@ijjk ijjk added the created-by: Turbopack team PRs by the Turbopack team. label Dec 5, 2024
@kdy1 kdy1 force-pushed the kdy1/issue-72232 branch 2 times, most recently from d13a976 to 0a45ac7 Compare December 9, 2024 14:46
@Iamknownasfesal
Copy link

when is this gonna get merged

This is a huge bug where we cannot even use graphql anymore

@arielweinberger
Copy link

arielweinberger commented Jan 31, 2025

Please, any news? To not implement ESM standards correctly with Turbopack and essentially block users from using various GraphQL packages with over 500k weekly downloads isn't cool.

@KyBerry
Copy link

KyBerry commented Jan 31, 2025

@arielweinberger

Please, any news? To not implement ESM standards correctly with Turbopack and essentially block users from using various GraphQL packages with over 500k weekly downloads isn't cool.

@Iamknownasfesal

when is this gonna get merged

This is a huge bug where we cannot even use graphql anymore

I'm not sure if you have a strict need to use turbopack, but removing --turbopack from the dev script so you just have "dev": "next dev" worked for me 🤷‍♂️

@Iamknownasfesal
Copy link

@arielweinberger

Please, any news? To not implement ESM standards correctly with Turbopack and essentially block users from using various GraphQL packages with over 500k weekly downloads isn't cool.

@Iamknownasfesal

when is this gonna get merged
This is a huge bug where we cannot even use graphql anymore

I'm not sure if you have a strict need to use turbopack, but removing --turbopack from the dev script so you just have "dev": "next dev" worked for me 🤷‍♂️

yea but any new nextjs developer will try to use turbopack, and look what they will see after they use qpl

@kdy1 kdy1 force-pushed the kdy1/issue-72232 branch from 0a45ac7 to 5d6507e Compare February 5, 2025 03:06
@ijjk ijjk added the Turbopack Related to Turbopack with Next.js. label Feb 5, 2025
@kdy1 kdy1 marked this pull request as ready for review February 5, 2025 03:46
@kdy1 kdy1 requested a review from sokra February 5, 2025 03:46
@kdy1 kdy1 marked this pull request as draft February 5, 2025 03:46
@kdy1 kdy1 marked this pull request as ready for review February 5, 2025 03:47
@ijjk
Copy link
Member

ijjk commented Feb 5, 2025

Failing test suites

Commit: ba088e4

pnpm test-start-turbo test/e2e/app-dir/app-routes-trailing-slash/app-routes-trailing-slash.test.ts (turbopack)

  • app-routes-trailing-slash > should handle trailing slash for edge runtime
  • app-routes-trailing-slash > should handle trailing slash for node runtime
Expand output

● app-routes-trailing-slash › should handle trailing slash for edge runtime

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-routes-trailing-slash › should handle trailing slash for node runtime

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

pnpm test test/integration/404-page-app/test/index.test.js (turbopack)

  • 404 Page Support with _app > development mode > should not show pages/404 GIP error if _app has GIP
Expand output

● 404 Page Support with _app › development mode › should not show pages/404 GIP error if _app has GIP

expect(received).toBe(expected) // Object.is equality

Expected: 404
Received: 500

  83 |       it('should not show pages/404 GIP error if _app has GIP', async () => {
  84 |         const res = await fetchViaHTTP(appPort, '/abc')
> 85 |         expect(res.status).toBe(404)
     |                            ^
  86 |         const $ = cheerio.load(await res.text())
  87 |         expect($('#404-title').text()).toBe('Hi There')
  88 |         expect(stderr).not.toMatch(gip404Err)

  at Object.toBe (integration/404-page-app/test/index.test.js:85:28)

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

pnpm test test/integration/app-dir-export/test/dynamic-missing-gsp-prod.test.ts (turbopack)

  • app dir - with output export - dynamic missing gsp prod > production mode > should error when dynamic route is missing generateStaticParams
Expand output

● app dir - with output export - dynamic missing gsp prod › production mode › should error when dynamic route is missing generateStaticParams

expect(received).toMatch(expected)

Expected substring: "Page \"/another/[slug]\" is missing \"generateStaticParams()\" so it cannot be used with \"output: export\" config."
Received string:    " ⚠ Linting is disabled.·
> Build error occurred
Error [ModuleBuildError]: ./packages/next/dist/esm/build/templates/app-route.js
Code generation for chunk item errored
An error occurred while generating the chunk item 72493·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 72493
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/client/components/hooks-server-context.js
Code generation for chunk item errored
An error occurred while generating the chunk item 94965·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 94965
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/client/components/static-generation-bailout.js
Code generation for chunk item errored
An error occurred while generating the chunk item 26206·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 26206
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/lib/batcher.js
Code generation for chunk item errored
An error occurred while generating the chunk item 89677·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 89677
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/lib/constants.js
Code generation for chunk item errored
An error occurred while generating the chunk item 19981·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 19981
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/lib/detached-promise.js
Code generation for chunk item errored
An error occurred while generating the chunk item 9172·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 9172
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/lib/metadata/metadata-constants.js
Code generation for chunk item errored
An error occurred while generating the chunk item 56881·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 56881
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/lib/scheduler.js
Code generation for chunk item errored
An error occurred while generating the chunk item 13991·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 13991
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/app-render/dynamic-rendering.js
Code generation for chunk item errored
An error occurred while generating the chunk item 35962·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 35962
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/base-http/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 76801·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 76801
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/client-component-renderer-logger.js
Code generation for chunk item errored
An error occurred while generating the chunk item 47411·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 47411
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/dynamic-rendering-utils.js
Code generation for chunk item errored
An error occurred while generating the chunk item 79079·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 79079
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/lib/clone-response.js
Code generation for chunk item errored
An error occurred while generating the chunk item 60350·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 60350
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/lib/dedupe-fetch.js
Code generation for chunk item errored
An error occurred while generating the chunk item 78871·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 78871
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/lib/patch-fetch.js
Code generation for chunk item errored
An error occurred while generating the chunk item 72182·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 72182
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/lib/trace/constants.js
Code generation for chunk item errored
An error occurred while generating the chunk item 65348·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 65348
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/lib/trace/tracer.js
Code generation for chunk item errored
An error occurred while generating the chunk item 59638·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 59638
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/pipe-readable.js
Code generation for chunk item errored
An error occurred while generating the chunk item 65615·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 65615
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/render-result.js
Code generation for chunk item errored
An error occurred while generating the chunk item 88041·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 88041
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/request-meta.js
Code generation for chunk item errored
An error occurred while generating the chunk item 82677·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 82677
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/response-cache/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 33946·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 33946
- Execution of <EcmascriptModuleLocalsChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/response-cache/types.js
Code generation for chunk item errored
An error occurred while generating the chunk item 69049·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 69049
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/response-cache/utils.js
Code generation for chunk item errored
An error occurred while generating the chunk item 81901·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 81901
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 82437·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 82437
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/stream-utils/encodedTags.js
Code generation for chunk item errored
An error occurred while generating the chunk item 59886·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 59886
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/stream-utils/node-web-streams-helper.js
Code generation for chunk item errored
An error occurred while generating the chunk item 44132·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 44132
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/stream-utils/uint8array-helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 12085·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 12085
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/web/error.js
Code generation for chunk item errored
An error occurred while generating the chunk item 45647·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 45647
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/web/next-url.js
Code generation for chunk item errored
An error occurred while generating the chunk item 86000·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 86000
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/web/spec-extension/adapters/next-request.js
Code generation for chunk item errored
An error occurred while generating the chunk item 44619·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 44619
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/web/spec-extension/request.js
Code generation for chunk item errored
An error occurred while generating the chunk item 71874·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 71874
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/server/web/utils.js
Code generation for chunk item errored
An error occurred while generating the chunk item 68849·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 68849
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/get-hostname.js
Code generation for chunk item errored
An error occurred while generating the chunk item 89655·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 89655
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/i18n/detect-domain-locale.js
Code generation for chunk item errored
An error occurred while generating the chunk item 75343·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 75343
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/i18n/normalize-locale-path.js
Code generation for chunk item errored
An error occurred while generating the chunk item 76254·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 76254
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/invariant-error.js
Code generation for chunk item errored
An error occurred while generating the chunk item 95149·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 95149
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/is-thenable.js
Code generation for chunk item errored
An error occurred while generating the chunk item 68365·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 68365
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/add-locale.js
Code generation for chunk item errored
An error occurred while generating the chunk item 28348·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 28348
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/add-path-prefix.js
Code generation for chunk item errored
An error occurred while generating the chunk item 76226·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 76226
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/add-path-suffix.js
Code generation for chunk item errored
An error occurred while generating the chunk item 33901·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 33901
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/format-next-pathname-info.js
Code generation for chunk item errored
An error occurred while generating the chunk item 9970·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 9970
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/get-next-pathname-info.js
Code generation for chunk item errored
An error occurred while generating the chunk item 59649·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 59649
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/parse-path.js
Code generation for chunk item errored
An error occurred while generating the chunk item 64826·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 64826
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/path-has-prefix.js
Code generation for chunk item errored
An error occurred while generating the chunk item 35120·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 35120
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/remove-path-prefix.js
Code generation for chunk item errored
An error occurred while generating the chunk item 48229·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 48229
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./packages/next/dist/esm/shared/lib/router/utils/remove-trailing-slash.js
Code generation for chunk item errored
An error occurred while generating the chunk item 89088·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 89088
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext···
./test/integration/app-dir-export/app/favicon--route-entry.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7239·
Caused by:
- failed to get the correct SyntaxContext·
Debug info:
- An error occurred while generating the chunk item 7239
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext··

  at processIssues (../dist/shared/lib/turbopack/utils.js:110:37)
  at handleRouteType (../dist/build/handle-entrypoints.js:273:42)
  at async (../dist/build/turbopack-build/impl.js:225:17)
  at async turbopackBuild (../dist/build/turbopack-build/impl.js:267:5)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20) {
    type: 'ModuleBuildError'
  }
  "
  at toMatch (integration/app-dir-export/test/utils.ts:186:29)
  at Object.<anonymous> (integration/app-dir-export/test/dynamic-missing-gsp-prod.test.ts:8:9)

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

pnpm test test/integration/auto-export-error-bail/test/index.test.js (turbopack)

  • Auto Export _error bail > production mode > should not opt-out of auto static optimization from invalid _error
Expand output

● Auto Export _error bail › production mode › should not opt-out of auto static optimization from invalid _error

expect(received).toBe(expected) // Object.is equality

Expected: 0
Received: 1

  19 |     const combinedOutput = output.stderr + output.stdout
  20 |
> 21 |     expect(output.code).toBe(0)
     |                         ^
  22 |     expect(combinedOutput).not.toContain(
  23 |       'You have opted-out of Automatic Static Optimization due to'
  24 |     )

  at Object.toBe (integration/auto-export-error-bail/test/index.test.js:21:25)

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

pnpm test test/integration/absolute-assetprefix/test/index.test.js (turbopack)

  • absolute assetPrefix with path prefix > production mode > should not fetch static data from a CDN
  • absolute assetPrefix with path prefix > production mode > should fetch from cache correctly
  • absolute assetPrefix with path prefix > production mode > should work with getStaticPaths prerendered
  • absolute assetPrefix with path prefix > production mode > should work with getStaticPaths fallback
  • absolute assetPrefix with path prefix > production mode > should work with getServerSideProps
Expand output

● absolute assetPrefix with path prefix › production mode › should not fetch static data from a CDN

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Building (0/5) ...
   Building (1/5) 
   Building (2/5) 
   Building (3/5) 
 ✓ Building (5/5)

> Build error occurred
Error: Turbopack build failed with 23 errors:
Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5912

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5912
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4305

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4305
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4330

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4330
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5453

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5453
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 8865

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 8865
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 7127

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7127
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 9491

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 9491
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5269

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5269
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1550

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1550
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1813

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1813
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 320

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 320
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4309

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4309
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7553

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7553
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at turbopackBuild (../dist/build/turbopack-build/impl.js:299:37)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20)
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

● absolute assetPrefix with path prefix › production mode › should fetch from cache correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Building (0/5) ...
   Building (1/5) 
   Building (2/5) 
   Building (3/5) 
 ✓ Building (5/5)

> Build error occurred
Error: Turbopack build failed with 23 errors:
Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5912

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5912
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4305

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4305
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4330

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4330
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5453

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5453
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 8865

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 8865
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 7127

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7127
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 9491

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 9491
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5269

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5269
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1550

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1550
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1813

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1813
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 320

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 320
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4309

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4309
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7553

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7553
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at turbopackBuild (../dist/build/turbopack-build/impl.js:299:37)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20)
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

● absolute assetPrefix with path prefix › production mode › should work with getStaticPaths prerendered

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Building (0/5) ...
   Building (1/5) 
   Building (2/5) 
   Building (3/5) 
 ✓ Building (5/5)

> Build error occurred
Error: Turbopack build failed with 23 errors:
Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5912

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5912
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4305

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4305
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4330

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4330
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5453

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5453
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 8865

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 8865
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 7127

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7127
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 9491

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 9491
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5269

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5269
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1550

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1550
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1813

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1813
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 320

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 320
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4309

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4309
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7553

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7553
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at turbopackBuild (../dist/build/turbopack-build/impl.js:299:37)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20)
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

● absolute assetPrefix with path prefix › production mode › should work with getStaticPaths fallback

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Building (0/5) ...
   Building (1/5) 
   Building (2/5) 
   Building (3/5) 
 ✓ Building (5/5)

> Build error occurred
Error: Turbopack build failed with 23 errors:
Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5912

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5912
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4305

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4305
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4330

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4330
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5453

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5453
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 8865

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 8865
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 7127

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7127
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 9491

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 9491
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5269

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5269
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1550

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1550
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1813

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1813
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 320

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 320
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4309

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4309
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7553

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7553
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at turbopackBuild (../dist/build/turbopack-build/impl.js:299:37)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20)
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

● absolute assetPrefix with path prefix › production mode › should work with getServerSideProps

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/absolute-assetprefix/next.config.js
   Building (0/5) ...
   Building (1/5) 
   Building (2/5) 
   Building (3/5) 
 ✓ Building (5/5)

> Build error occurred
Error: Turbopack build failed with 23 errors:
Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5912

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5912
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4305

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4305
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4330

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4330
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/"}
./test/integration/absolute-assetprefix/pages/index.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5453

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5453
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 8865

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 8865
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 7127

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7127
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gsp-fallback/[slug]"}
./test/integration/absolute-assetprefix/pages/gsp-fallback/[slug].js
Code generation for chunk item errored
An error occurred while generating the chunk item 9491

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 9491
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5269

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5269
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1550

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1550
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/about"}
./test/integration/absolute-assetprefix/pages/about.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1813

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1813
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 320

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 320
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4309

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4309
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/gssp"}
./test/integration/absolute-assetprefix/pages/gssp.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7553

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7553
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at turbopackBuild (../dist/build/turbopack-build/impl.js:299:37)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20)
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

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

pnpm test test/integration/dist-dir/test/index.test.js (turbopack)

  • distDir > development mode > should render the page
Expand output

● distDir › development mode › should render the page

expect(received).toMatch(expected)

Expected pattern: /Hello World/
Received string:  "<!DOCTYPE html><html><head><meta charSet=\"utf-8\" data-next-head=\"\"/><meta name=\"viewport\" content=\"width=device-width\" data-next-head=\"\"/><style data-next-hide-fouc=\"true\">body{display:none}</style><noscript data-next-hide-fouc=\"true\"><style>body{display:block}</style></noscript><noscript data-n-css=\"\"></noscript><script src=\"/_next/static/chunks/%5Broot%20of%20the%20server%5D__e3e8d8fa._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/node_modules__pnpm_42b81cb4._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_dist-dir_pages__app_5771e187._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_dist-dir_pages__app_930bb508._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_compiled_980db5f0._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_shared_lib_a2a578c0._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_client_fa4530ff._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_fc82a218._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_error_a875dfda.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_dist-dir_pages__error_19ff3b93._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/%5Broot%20of%20the%20server%5D__4aaba451._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_dist-dir_pages__error_5771e187._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_dist-dir_pages__error_d12e3345._.js\" defer=\"\"></script><script src=\"/_next/static/development/_ssgManifest.js\" defer=\"\"></script><script src=\"/_next/static/development/_buildManifest.js\" defer=\"\"></script><noscript id=\"__next_css__DO_NOT_USE__\"></noscript></head><body><div id=\"__next\"></div><script id=\"__NEXT_DATA__\" type=\"application/json\">{\"props\":{\"pageProps\":{\"statusCode\":500,\"hostname\":\"[::]\"}},\"page\":\"/_error\",\"query\":{},\"buildId\":\"development\",\"isFallback\":false,\"err\":{\"name\":\"Error\",\"source\":\"server\",\"message\":\"[turbopack]/browser/dev/hmr-client/hmr-client.ts\\nCode generation for chunk item errored\\nAn error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n\\nCaused by:\\n- failed to get the correct SyntaxContext\\n\\nDebug info:\\n- An error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n- Execution of \\u003cModuleChunkItem as EcmascriptChunkItem\\u003e::content_with_async_module_info failed\\n- Execution of EcmascriptModuleContent::new failed\\n- failed to get the correct SyntaxContext\\n\\n\",\"stack\":\"Error: [turbopack]/browser/dev/hmr-client/hmr-client.ts\\nCode generation for chunk item errored\\nAn error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n\\nCaused by:\\n- failed to get the correct SyntaxContext\\n\\nDebug info:\\n- An error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n- Execution of \\u003cModuleChunkItem as EcmascriptChunkItem\\u003e::content_with_async_module_info failed\\n- Execution of EcmascriptModuleContent::new failed\\n- failed to get the correct SyntaxContext\\n\\n\\n    at Object.getCompilationErrors (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/dev/hot-reloader-turbopack.js:722:59)\\n    at DevBundlerService.getCompilationError (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/lib/dev-bundler-service.js:39:55)\\n    at DevServer.getCompilationError (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/dev/next-dev-server.js:643:42)\\n    at DevServer.findPageComponents (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/dev/next-dev-server.js:613:43)\\n    at async DevServer.renderErrorToResponseImpl (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/base-server.js:2576:26)\"},\"gip\":true,\"scriptLoader\":[]}</script></body></html>"

  61 |       it('should render the page', async () => {
  62 |         const html = await renderViaHTTP(appPort, '/')
> 63 |         expect(html).toMatch(/Hello World/)
     |                      ^
  64 |       })
  65 |
  66 |       it('should build the app within the given `dist` directory', async () => {

  at Object.toMatch (integration/dist-dir/test/index.test.js:63:22)

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

pnpm test-start-turbo test/e2e/app-dir/app-fetch-deduping/app-fetch-deduping.test.ts (turbopack)

  • app-fetch-deduping > during static generation > dedupes requests amongst static workers
Expand output

● app-fetch-deduping › during static generation › dedupes requests amongst static workers

expect(received).toBe(expected) // Object.is equality

Expected: 1
Received: 0

  54 |         )
  55 |         await next.build()
> 56 |         expect(successfulRequests.length).toBe(1)
     |                                           ^
  57 |       })
  58 |     })
  59 |   } else if (isNextDev) {

  at Object.toBe (e2e/app-dir/app-fetch-deduping/app-fetch-deduping.test.ts:56:43)

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

pnpm test test/integration/basepath-root-catch-all/test/index.test.js (turbopack)

  • production mode > should use correct data URL for root catch-all
Expand output

● production mode › should use correct data URL for root catch-all

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/basepath-root-catch-all/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/basepath-root-catch-all/next.config.js
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/basepath-root-catch-all/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/basepath-root-catch-all/next.config.js
   Building (0/3) ...
 ✓ Building (3/3)

> Build error occurred
Error: Turbopack build failed with 13 errors:
Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5912

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5912
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"_error"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/[...parts]"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/[...parts]"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5324

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5324
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/[...parts]"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/[...parts]"}
./test/integration/basepath-root-catch-all/pages/[...parts].js
Code generation for chunk item errored
An error occurred while generating the chunk item 6872

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6872
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/[...parts]"}
./test/integration/basepath-root-catch-all/pages/[...parts].js
Code generation for chunk item errored
An error occurred while generating the chunk item 701

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 701
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/hello"}
./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6167

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6167
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/hello"}
./packages/next/dist/esm/build/templates/pages.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6222

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6222
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/hello"}
./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 5454

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 5454
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/hello"}
./test/integration/basepath-root-catch-all/pages/hello.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4853

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4853
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext


Page: {"type":"pages","side":"server","page":"/hello"}
./test/integration/basepath-root-catch-all/pages/hello.js
Code generation for chunk item errored
An error occurred while generating the chunk item 7225

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 7225
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at turbopackBuild (../dist/build/turbopack-build/impl.js:299:37)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20)
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

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

pnpm test-dev-turbo test/development/app-dir/dev-fetch-hmr/dev-fetch-hmr.test.ts (turbopack)

  • dev-fetch-hmr > should retain module level fetch patching
Expand output

● dev-fetch-hmr › should retain module level fetch patching

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

Expected substring: "monkey patching is fun"
Received string:    "<!DOCTYPE html><html><head><meta charSet=\"utf-8\" data-next-head=\"\"/><meta name=\"viewport\" content=\"width=device-width\" data-next-head=\"\"/><style data-next-hide-fouc=\"true\">body{display:none}</style><noscript data-next-hide-fouc=\"true\"><style>body{display:block}</style></noscript><noscript data-n-css=\"\"></noscript><script src=\"/_next/static/chunks/c5d66_next_dist_compiled_2d0fdcc4._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_dist_shared_lib_7c854c05._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_dist_client_ceb4710c._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_dist_2cf648b4._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_app_ad18a5d5.js\" defer=\"\"></script><script src=\"/_next/static/chunks/%5Bnext%5D_entry_page-loader_ts_b7999d3d._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/545c3_react-dom_1c85ba3a._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/node_modules__pnpm_f84813a4._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/%5Broot%20of%20the%20server%5D__49fd8634._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/pages__app_5771e187._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/pages__app_95004ed3._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_dist_shared_lib_bc66e0d8._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_dist_c4f14989._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/c5d66_next_error_dc59e884.js\" defer=\"\"></script><script src=\"/_next/static/chunks/%5Bnext%5D_entry_page-loader_ts_781cb306._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/%5Broot%20of%20the%20server%5D__923cb372._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/pages__error_5771e187._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/pages__error_5fd5842b._.js\" defer=\"\"></script><script src=\"/_next/static/development/_ssgManifest.js\" defer=\"\"></script><script src=\"/_next/static/development/_buildManifest.js\" defer=\"\"></script><noscript id=\"__next_css__DO_NOT_USE__\"></noscript></head><body><div id=\"__next\"></div><script id=\"__NEXT_DATA__\" type=\"application/json\">{\"props\":{\"pageProps\":{\"statusCode\":500,\"hostname\":\"localhost\"}},\"page\":\"/_error\",\"query\":{},\"buildId\":\"development\",\"isFallback\":false,\"err\":{\"name\":\"Error\",\"source\":\"server\",\"message\":\"./app/layout.tsx\\nCode generation for chunk item errored\\nAn error occurred while generating the chunk item [project]/app/layout.tsx [app-rsc] (ecmascript)\\n\\nCaused by:\\n- failed to get the correct SyntaxContext\\n\\nDebug info:\\n- An error occurred while generating the chunk item [project]/app/layout.tsx [app-rsc] (ecmascript)\\n- Execution of \\u003cModuleChunkItem as EcmascriptChunkItem\\u003e::content_with_async_module_info failed\\n- Execution of EcmascriptModuleContent::new failed\\n- failed to get the correct SyntaxContext\\n\\n\",\"stack\":\"Error: ./app/layout.tsx\\nCode generation for chunk item errored\\nAn error occurred while generating the chunk item [project]/app/layout.tsx [app-rsc] (ecmascript)\\n\\nCaused by:\\n- failed to get the correct SyntaxContext\\n\\nDebug info:\\n- An error occurred while generating the chunk item [project]/app/layout.tsx [app-rsc] (ecmascript)\\n- Execution of \\u003cModuleChunkItem as EcmascriptChunkItem\\u003e::content_with_async_module_info failed\\n- Execution of EcmascriptModuleContent::new failed\\n- failed to get the correct SyntaxContext\\n\\n\\n    at Object.getCompilationErrors (/tmp/next-install-464f771e2bf3d4664e3795474bf3681507156e0ef8f6cff5225f4640a9cd17f3/node_modules/.pnpm/next@file+..+next-repo-6230f450171d86e2f380af60740da485a8dbbd67c38f06194eed71b3ef894665+packa_xjinmftnminwt77bmqwjiru35m/node_modules/next/dist/server/dev/hot-reloader-turbopack.js:722:59)\\n    at DevBundlerService.getCompilationError (/tmp/next-install-464f771e2bf3d4664e3795474bf3681507156e0ef8f6cff5225f4640a9cd17f3/node_modules/.pnpm/next@file+..+next-repo-6230f450171d86e2f380af60740da485a8dbbd67c38f06194eed71b3ef894665+packa_xjinmftnminwt77bmqwjiru35m/node_modules/next/dist/server/lib/dev-bundler-service.js:39:55)\\n    at DevServer.getCompilationError (/tmp/next-install-464f771e2bf3d4664e3795474bf3681507156e0ef8f6cff5225f4640a9cd17f3/node_modules/.pnpm/next@file+..+next-repo-6230f450171d86e2f380af60740da485a8dbbd67c38f06194eed71b3ef894665+packa_xjinmftnminwt77bmqwjiru35m/node_modules/next/dist/server/dev/next-dev-server.js:643:42)\\n    at DevServer.findPageComponents (/tmp/next-install-464f771e2bf3d4664e3795474bf3681507156e0ef8f6cff5225f4640a9cd17f3/node_modules/.pnpm/next@file+..+next-repo-6230f450171d86e2f380af60740da485a8dbbd67c38f06194eed71b3ef894665+packa_xjinmftnminwt77bmqwjiru35m/node_modules/next/dist/server/dev/next-dev-server.js:613:43)\\n    at async DevServer.renderErrorToResponseImpl (/tmp/next-install-464f771e2bf3d4664e3795474bf3681507156e0ef8f6cff5225f4640a9cd17f3/node_modules/.pnpm/next@file+..+next-repo-6230f450171d86e2f380af60740da485a8dbbd67c38f06194eed71b3ef894665+packa_xjinmftnminwt77bmqwjiru35m/node_modules/next/dist/server/base-server.js:2576:26)\"},\"gip\":true,\"scriptLoader\":[]}</script></body></html>"

  11 |   it('should retain module level fetch patching', async () => {
  12 |     const html = await next.render('/')
> 13 |     expect(html).toContain('monkey patching is fun')
     |                  ^
  14 |
  15 |     const magicNumber = cheerio.load(html)('#magic-number').text()
  16 |

  at Object.toContain (development/app-dir/dev-fetch-hmr/dev-fetch-hmr.test.ts:13:18)

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

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

  • actions-revalidate-remount > should not remount the page + loading component when revalidating
Expand output

● actions-revalidate-remount › should not remount the page + loading component when revalidating

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

pnpm test-start-turbo test/e2e/app-dir/app-routes/app-custom-route-base-path.test.ts (turbopack)

  • app-custom-routes > automatic implementations > implements HEAD on routes with GET already implemented
  • app-custom-routes > automatic implementations > implements OPTIONS on routes
  • app-custom-routes > basic fetch request with a response > abort via a DELETE request > aborts without error on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a DELETE request > aborts without error on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a GET request > aborts without error on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a GET request > aborts without error on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a PATCH request > aborts without error on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a PATCH request > aborts without error on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a POST request > aborts without error on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a POST request > aborts without error on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a PUT request > aborts without error on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > abort via a PUT request > aborts without error on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > made via a DELETE request > responds correctly on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > made via a DELETE request > responds correctly on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > made via a GET request > responds correctly on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > made via a GET request > responds correctly on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > made via a PATCH request > responds correctly on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > made via a PATCH request > responds correctly on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > made via a POST request > responds correctly on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > made via a POST request > responds correctly on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > made via a PUT request > responds correctly on /basic/endpoint
  • app-custom-routes > basic fetch request with a response > made via a PUT request > responds correctly on /basic/vercel/endpoint
  • app-custom-routes > basic fetch request with a response > request > can read query parameters
  • app-custom-routes > basic fetch request with a response > request > can read query parameters (edge)
  • app-custom-routes > basic fetch request with a response > response > supports the NextResponse.redirect() helper
  • app-custom-routes > basic fetch request with a response > response > supports the NextResponse.json() helper
  • app-custom-routes > basic fetch request with a response > route groups > routes to the correct handler
  • app-custom-routes > body > can handle handle a streaming request and streaming response
  • app-custom-routes > body > can handle handle a streaming request and streaming response (edge)
  • app-custom-routes > body > can read a JSON encoded body
  • app-custom-routes > body > can read a JSON encoded body (edge)
  • app-custom-routes > body > can read a JSON encoded body for DELETE requests
  • app-custom-routes > body > can read a JSON encoded body for OPTIONS requests
  • app-custom-routes > body > can read a streamed JSON encoded body
  • app-custom-routes > body > can read a streamed JSON encoded body (edge)
  • app-custom-routes > body > can read the text body
  • app-custom-routes > body > can read the text body (edge)
  • app-custom-routes > context > provides params to routes with dynamic parameters
  • app-custom-routes > context > provides params to routes with catch-all routes
  • app-custom-routes > context > does not provide params to routes without dynamic parameters
  • app-custom-routes > customized metadata routes > should work if conflict with metadata routes convention
  • app-custom-routes > dynamic = "force-static" > strips search, headers, and domain from request
  • app-custom-routes > edge functions > returns response using edge runtime
  • app-custom-routes > edge functions > returns a response when headers are accessed
  • app-custom-routes > error conditions > responds with 400 (Bad Request) when the requested method is not a valid HTTP method
  • app-custom-routes > error conditions > responds with 405 (Method Not Allowed) when method is not implemented
  • app-custom-routes > error conditions > responds with 500 (Internal Server Error) when the handler throws an error
  • app-custom-routes > error conditions > responds with 500 (Internal Server Error) when the handler calls NextResponse.next()
  • app-custom-routes > hooks > (await cookies()).has() > gets the correct values
  • app-custom-routes > hooks > cookies > gets the correct values
  • app-custom-routes > hooks > headers > gets the correct values
  • app-custom-routes > hooks > notFound > can respond correctly in nodejs
  • app-custom-routes > hooks > notFound > can respond correctly in edge
  • app-custom-routes > hooks > permanentRedirect > can respond correctly
  • app-custom-routes > hooks > redirect > can respond correctly
  • app-custom-routes > hooks > req.cookies > gets the correct values
  • app-custom-routes > no bundle error > should not print bundling warning about React
  • app-custom-routes > no response returned > should print an error when no response is returned
  • app-custom-routes > works with api prefix correctly > statically generates correctly with no dynamic usage
  • app-custom-routes > works with api prefix correctly > does not statically generate with dynamic usage
  • app-custom-routes > works with generateStaticParams correctly > responds correctly on /static/first/data.json
  • app-custom-routes > works with generateStaticParams correctly > responds correctly on /static/second/data.json
  • app-custom-routes > works with generateStaticParams correctly > responds correctly on /static/three/data.json
  • app-custom-routes > works with generateStaticParams correctly > revalidates correctly on /revalidate-1/first/data.json
  • app-custom-routes > works with generateStaticParams correctly > revalidates correctly on /revalidate-1/second/data.json
  • app-custom-routes > works with generateStaticParams correctly > revalidates correctly on /revalidate-1/three/data.json
Expand output

● app-custom-routes › works with api prefix correctly › statically generates correctly with no dynamic usage

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with api prefix correctly › does not statically generate with dynamic usage

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with generateStaticParams correctly › responds correctly on /static/first/data.json

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with generateStaticParams correctly › responds correctly on /static/second/data.json

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with generateStaticParams correctly › responds correctly on /static/three/data.json

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with generateStaticParams correctly › revalidates correctly on /revalidate-1/first/data.json

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with generateStaticParams correctly › revalidates correctly on /revalidate-1/second/data.json

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › works with generateStaticParams correctly › revalidates correctly on /revalidate-1/three/data.json

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a GET request › responds correctly on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a GET request › responds correctly on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a POST request › responds correctly on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a POST request › responds correctly on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a PUT request › responds correctly on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a PUT request › responds correctly on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a DELETE request › responds correctly on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a DELETE request › responds correctly on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a PATCH request › responds correctly on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › made via a PATCH request › responds correctly on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a GET request › aborts without error on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a GET request › aborts without error on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a POST request › aborts without error on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a POST request › aborts without error on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a PUT request › aborts without error on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a PUT request › aborts without error on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a DELETE request › aborts without error on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a DELETE request › aborts without error on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a PATCH request › aborts without error on /basic/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › abort via a PATCH request › aborts without error on /basic/vercel/endpoint

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › route groups › routes to the correct handler

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › request › can read query parameters

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › request › can read query parameters (edge)

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › response › supports the NextResponse.rewrite() helper

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › response › supports the NextResponse.redirect() helper

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › basic fetch request with a response › response › supports the NextResponse.json() helper

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can handle handle a streaming request and streaming response

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can handle handle a streaming request and streaming response (edge)

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read a JSON encoded body

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read a JSON encoded body (edge)

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read a JSON encoded body for DELETE requests

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read a JSON encoded body for OPTIONS requests

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read a streamed JSON encoded body

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read a streamed JSON encoded body (edge)

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read the text body

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › body › can read the text body (edge)

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › context › provides params to routes with dynamic parameters

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › context › provides params to routes with catch-all routes

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › context › does not provide params to routes without dynamic parameters

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › headers › gets the correct values

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › cookies › gets the correct values

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › req.cookies › gets the correct values

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › (await cookies()).has() › gets the correct values

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › redirect › can respond correctly

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › permanentRedirect › can respond correctly

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › notFound › can respond correctly in nodejs

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › hooks › notFound › can respond correctly in edge

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › error conditions › responds with 400 (Bad Request) when the requested method is not a valid HTTP method

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › error conditions › responds with 405 (Method Not Allowed) when method is not implemented

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › error conditions › responds with 500 (Internal Server Error) when the handler throws an error

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › error conditions › responds with 500 (Internal Server Error) when the handler calls NextResponse.next()

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › automatic implementations › implements HEAD on routes with GET already implemented

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › automatic implementations › implements OPTIONS on routes

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › edge functions › returns response using edge runtime

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › edge functions › returns a response when headers are accessed

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › dynamic = "force-static" › strips search, headers, and domain from request

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › customized metadata routes › should work if conflict with metadata routes convention

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › no response returned › should print an error when no response is returned

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-custom-routes › no bundle error › should not print bundling warning about React

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

pnpm test-start-turbo test/e2e/app-dir/app-routes-subrequests/app-routes-subrequests.test.ts (turbopack)

  • app-routes-subrequests > shortcuts after 5 subrequests
Expand output

● app-routes-subrequests › shortcuts after 5 subrequests

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

pnpm test-start-turbo test/e2e/app-dir/app-edge-root-layout/index.test.ts (turbopack)

  • app-dir edge runtime root layout > should not emit metadata files into bad paths
  • app-dir edge runtime root layout > should mark static contain metadata routes as edge functions
Expand output

● app-dir edge runtime root layout › should not emit metadata files into bad paths

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-dir edge runtime root layout › should mark static contain metadata routes as edge functions

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:108: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

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app dir - basepath › should support basePath

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:108: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

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

  at ChildProcess.<anonymous> (lib/next-modes/next-start.ts:108: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

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

pnpm test-dev test/development/next-config-ts/turbo/index.test.ts

  • next-config-ts - turbopack > should work with Turbopack
Expand output

● next-config-ts - turbopack › should work with Turbopack

expect(received).toBe(expected) // Object.is equality

Expected: "foo"
Received: ""

   9 |   it('should work with Turbopack', async () => {
  10 |     const $ = await next.render$('/')
> 11 |     expect($('p').text()).toBe('foo')
     |                           ^
  12 |   })
  13 | })
  14 |

  at Object.toBe (development/next-config-ts/turbo/index.test.ts:11:27)

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

pnpm test-dev-turbo test/development/acceptance-app/dynamic-error.test.ts (turbopack)

  • dynamic = "error" in devmode > should show error overlay when dynamic is forced
Expand output

● dynamic = "error" in devmode › should show error overlay when dynamic is forced

Expected Redbox but found no visible one.

  31 |     )
  32 |     const { session } = sandbox
> 33 |     await session.assertHasRedbox()
     |     ^
  34 |     const description = await session.getRedboxDescription()
  35 |     expect(description).toMatchInlineSnapshot(
  36 |       `"Error: Route /server with \`dynamic = "error"\` couldn't be rendered statically because it used \`cookies\`. See more info here: https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering"`

  at Object.<anonymous> (development/acceptance-app/dynamic-error.test.ts:33:5)

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

pnpm test-dev-turbo test/development/acceptance-app/editor-links.test.ts (turbopack)

  • Error overlay - editor links > should be possible to open source file on build error
Expand output

● Error overlay - editor links › should be possible to open source file on build error

Application is in inconsistent state: timeout.

  92 |             }
  93 |             if (status !== 'pending') {
> 94 |               throw new Error(
     |                     ^
  95 |                 `Application is in inconsistent state: ${status}.`
  96 |               )
  97 |             }

  at Object.patch (lib/development-sandbox.ts:94:21)
  at Object.<anonymous> (development/acceptance-app/editor-links.test.ts:60:5)

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

pnpm test-dev-turbo test/development/acceptance/ReactRefreshModule.test.ts (turbopack)

  • ReactRefreshModule > should allow any variable names
Expand output

● ReactRefreshModule › should allow any variable names

Application is in inconsistent state: timeout.

  92 |             }
  93 |             if (status !== 'pending') {
> 94 |               throw new Error(
     |                     ^
  95 |                 `Application is in inconsistent state: ${status}.`
  96 |               )
  97 |             }

  at Object.patch (lib/development-sandbox.ts:94:21)
  at Object.<anonymous> (development/acceptance/ReactRefreshModule.test.ts:25:7)

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

pnpm test-dev-turbo test/development/app-dir/dev-indicator/hide-button.test.ts (turbopack)

  • dev indicator - Hide DevTools Button > should show the dev indicator when the server is manually restarted
  • dev indicator - Hide DevTools Button > should still hide the dev indicator after reloading the page
  • dev indicator - Hide DevTools Button > should show the dev indicator after cooldown period has passed
Expand output

● dev indicator - Hide DevTools Button › should show the dev indicator when the server is manually restarted

Expected DevTools Indicator but found no visible one.

  959 |   browser: BrowserInterface
  960 | ): Promise<void> {
> 961 |   const devToolsIndicator = await assertHasDevToolsIndicator(browser)
      |                             ^
  962 |
  963 |   try {
  964 |     await devToolsIndicator.click()

  at openDevToolsIndicatorPopover (lib/next-test-utils.ts:961:29)
  at Object.<anonymous> (development/app-dir/dev-indicator/hide-button.test.ts:22:5)

● dev indicator - Hide DevTools Button › should still hide the dev indicator after reloading the page

Expected DevTools Indicator but found no visible one.

  959 |   browser: BrowserInterface
  960 | ): Promise<void> {
> 961 |   const devToolsIndicator = await assertHasDevToolsIndicator(browser)
      |                             ^
  962 |
  963 |   try {
  964 |     await devToolsIndicator.click()

  at openDevToolsIndicatorPopover (lib/next-test-utils.ts:961:29)
  at Object.<anonymous> (development/app-dir/dev-indicator/hide-button.test.ts:39:5)

● dev indicator - Hide DevTools Button › should show the dev indicator after cooldown period has passed

Expected DevTools Indicator but found no visible one.

  959 |   browser: BrowserInterface
  960 | ): Promise<void> {
> 961 |   const devToolsIndicator = await assertHasDevToolsIndicator(browser)
      |                             ^
  962 |
  963 |   try {
  964 |     await devToolsIndicator.click()

  at openDevToolsIndicatorPopover (lib/next-test-utils.ts:961:29)
  at Object.<anonymous> (development/app-dir/dev-indicator/hide-button.test.ts:55:5)

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

pnpm test test/integration/catches-missing-getStaticProps/test/index.test.js (turbopack)

  • Catches Missing getStaticProps > development mode > should catch it in development mode
Expand output

● Catches Missing getStaticProps › development mode › should catch it in development mode

expect(received).toMatch(expected)

Expected pattern: /getStaticPaths was added without a getStaticProps in/
Received string:  "<!DOCTYPE html><html><head><meta charSet=\"utf-8\" data-next-head=\"\"/><meta name=\"viewport\" content=\"width=device-width\" data-next-head=\"\"/><style data-next-hide-fouc=\"true\">body{display:none}</style><noscript data-next-hide-fouc=\"true\"><style>body{display:block}</style></noscript><noscript data-n-css=\"\"></noscript><script src=\"/_next/static/chunks/%5Broot%20of%20the%20server%5D__2ae19907._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/node_modules__pnpm_42b81cb4._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_catches-missing-getStaticProps_pages__app_5771e187._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_catches-missing-getStaticProps_pages__app_d660b756._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_compiled_980db5f0._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_shared_lib_a2a578c0._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_client_fa4530ff._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_dist_fc82a218._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/packages_next_error_a875dfda.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_catches-missing-getStaticProps_pages__error_af76941c._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/%5Broot%20of%20the%20server%5D__4aaba451._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_catches-missing-getStaticProps_pages__error_5771e187._.js\" defer=\"\"></script><script src=\"/_next/static/chunks/test_integration_catches-missing-getStaticProps_pages__error_7d02e8ef._.js\" defer=\"\"></script><script src=\"/_next/static/development/_ssgManifest.js\" defer=\"\"></script><script src=\"/_next/static/development/_buildManifest.js\" defer=\"\"></script><noscript id=\"__next_css__DO_NOT_USE__\"></noscript></head><body><div id=\"__next\"></div><script id=\"__NEXT_DATA__\" type=\"application/json\">{\"props\":{\"pageProps\":{\"statusCode\":500,\"hostname\":\"[::]\"}},\"page\":\"/_error\",\"query\":{},\"buildId\":\"development\",\"isFallback\":false,\"err\":{\"name\":\"Error\",\"source\":\"server\",\"message\":\"[turbopack]/browser/dev/hmr-client/hmr-client.ts\\nCode generation for chunk item errored\\nAn error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n\\nCaused by:\\n- failed to get the correct SyntaxContext\\n\\nDebug info:\\n- An error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n- Execution of \\u003cModuleChunkItem as EcmascriptChunkItem\\u003e::content_with_async_module_info failed\\n- Execution of EcmascriptModuleContent::new failed\\n- failed to get the correct SyntaxContext\\n\\n\",\"stack\":\"Error: [turbopack]/browser/dev/hmr-client/hmr-client.ts\\nCode generation for chunk item errored\\nAn error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n\\nCaused by:\\n- failed to get the correct SyntaxContext\\n\\nDebug info:\\n- An error occurred while generating the chunk item [turbopack]/browser/dev/hmr-client/hmr-client.ts [client] (ecmascript)\\n- Execution of \\u003cModuleChunkItem as EcmascriptChunkItem\\u003e::content_with_async_module_info failed\\n- Execution of EcmascriptModuleContent::new failed\\n- failed to get the correct SyntaxContext\\n\\n\\n    at Object.getCompilationErrors (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/dev/hot-reloader-turbopack.js:722:59)\\n    at DevBundlerService.getCompilationError (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/lib/dev-bundler-service.js:39:55)\\n    at DevServer.getCompilationError (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/dev/next-dev-server.js:643:42)\\n    at DevServer.findPageComponents (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/dev/next-dev-server.js:613:43)\\n    at async DevServer.renderErrorToResponseImpl (/root/actions-runner/_work/next.js/next.js/packages/next/dist/server/base-server.js:2576:26)\"},\"gip\":true,\"scriptLoader\":[]}</script></body></html>"

  23 |         await killApp(app)
  24 |
> 25 |         expect(html).toMatch(errorRegex)
     |                      ^
  26 |       })
  27 |     }
  28 |   )

  at Object.toMatch (integration/catches-missing-getStaticProps/test/index.test.js:25:22)

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

pnpm test test/integration/api-body-parser/test/index.test.js (turbopack)

  • should parse JSON body

  • should not throw if request body is already parsed in custom middleware

  • should not throw if request's content-type is invalid

Expand output

● should parse JSON body

expect(received).toEqual(expected) // deep equality

Expected: [{"title": "Nextjs"}]
Received: false

  24 |     app = await launchApp(appDir, appPort, {})
  25 |     const data = await makeRequest()
> 26 |     expect(data).toEqual([{ title: 'Nextjs' }])
     |                  ^
  27 |     await killApp(app)
  28 |   })
  29 |

  at Object.toEqual (integration/api-body-parser/test/index.test.js:26:18)

● should not throw if request body is already parsed in custom middleware

expect(received).toEqual(expected) // deep equality

Expected: [{"title": "Nextjs"}]
Received: false

  31 |     await startServer()
  32 |     const data = await makeRequest()
> 33 |     expect(data).toEqual([{ title: 'Nextjs' }])
     |                  ^
  34 |     await killApp(server)
  35 |   })
  36 |

  at Object.toEqual (integration/api-body-parser/test/index.test.js:33:18)

● should not throw if request's content-type is invalid

expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 500

  38 |     await startServer()
  39 |     const status = await makeRequestWithInvalidContentType()
> 40 |     expect(status).toBe(200)
     |                    ^
  41 |     await killApp(server)
  42 |   })
  43 | }

  at Object.toBe (integration/api-body-parser/test/index.test.js:40:20)

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

pnpm test test/integration/api-catch-all/test/index.test.js (turbopack)

  • API routes > dev support > should return data when catch-all
  • API routes > dev support > should return data when catch-all with index and trailing slash
  • API routes > dev support > should return data when catch-all with index and no trailing slash
Expand output

● API routes › dev support › should return data when catch-all

expect(received).toEqual(expected) // deep equality

Expected: {"slug": ["1"]}
Received: false

  20 |     )
  21 |
> 22 |     expect(data).toEqual({ slug: ['1'] })
     |                  ^
  23 |   })
  24 |
  25 |   it('should return redirect when catch-all with index and trailing slash', async () => {

  at Object.toEqual (integration/api-catch-all/test/index.test.js:22:18)

● API routes › dev support › should return data when catch-all with index and trailing slash

expect(received).toEqual(expected) // deep equality

Expected: {}
Received: false

  38 |     )
  39 |
> 40 |     expect(data).toEqual({})
     |                  ^
  41 |   })
  42 |
  43 |   it('should return data when catch-all with index and no trailing slash', async () => {

  at Object.toEqual (integration/api-catch-all/test/index.test.js:40:18)

● API routes › dev support › should return data when catch-all with index and no trailing slash

expect(received).toEqual(expected) // deep equality

Expected: {}
Received: false

  46 |     )
  47 |
> 48 |     expect(data).toEqual({})
     |                  ^
  49 |   })
  50 | }
  51 |

  at Object.toEqual (integration/api-catch-all/test/index.test.js:48:18)

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

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

  • app-dir - esm js extension > should be able to render nextjs api in app router
  • app-dir - esm js extension > should be able to use nextjs api in pages router
  • app-dir - esm js extension > should support next/og image
Expand output

● app-dir - esm js extension › should be able to render nextjs api in app router

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-dir - esm js extension › should be able to use nextjs api in pages router

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

● app-dir - esm js extension › should support next/og image

next build failed with code/signal 1

  106 |           if (code || signal)
  107 |             reject(
> 108 |               new Error(`next build failed with code/signal ${code || signal}`)
      |               ^
  109 |             )
  110 |           else resolve()
  111 |         })

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

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

pnpm test test/integration/bigint/test/index.test.js (turbopack)

  • bigint API route support > production mode > should return 200
  • bigint API route support > production mode > should return the BigInt result text
Expand output

● bigint API route support › production mode › should return 200

command failed with code 1 signal null
 ⚠ Linting is disabled.
   No config file found
   No config file found
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   No config file found
   No config file found
   Building (0/2) ...

> Build error occurred
Error [ModuleBuildError]: ./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6753

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6753
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext



./packages/next/dist/esm/build/templates/pages-api.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4153

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4153
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext



./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4624

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4624
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext



./test/integration/bigint/pages/api/bigint.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1942

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1942
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at processIssues (../dist/shared/lib/turbopack/utils.js:110:37)
  at handleRouteType (../dist/build/handle-entrypoints.js:228:42)
  at async (../dist/build/turbopack-build/impl.js:225:17)
  at async turbopackBuild (../dist/build/turbopack-build/impl.js:267:5)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20) {
    type: 'ModuleBuildError'
  }
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

● bigint API route support › production mode › should return the BigInt result text

command failed with code 1 signal null
 ⚠ Linting is disabled.
   No config file found
   No config file found
   ▲ Next.js 15.2.1-canary.2 (Turbopack)

   Checking validity of types ...
   Creating an optimized production build ...
   No config file found
   No config file found
   Building (0/2) ...

> Build error occurred
Error [ModuleBuildError]: ./packages/next/dist/esm/build/templates/helpers.js
Code generation for chunk item errored
An error occurred while generating the chunk item 6753

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 6753
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext



./packages/next/dist/esm/build/templates/pages-api.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4153

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4153
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext



./packages/next/dist/esm/server/route-kind.js
Code generation for chunk item errored
An error occurred while generating the chunk item 4624

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 4624
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext



./test/integration/bigint/pages/api/bigint.js
Code generation for chunk item errored
An error occurred while generating the chunk item 1942

Caused by:
- failed to get the correct SyntaxContext

Debug info:
- An error occurred while generating the chunk item 1942
- Execution of <ModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
- Execution of EcmascriptModuleContent::new failed
- failed to get the correct SyntaxContext

  at processIssues (../dist/shared/lib/turbopack/utils.js:110:37)
  at handleRouteType (../dist/build/handle-entrypoints.js:228:42)
  at async (../dist/build/turbopack-build/impl.js:225:17)
  at async turbopackBuild (../dist/build/turbopack-build/impl.js:267:5)
  at async Object.workerMain (../dist/build/turbopack-build/impl.js:331:20) {
    type: 'ModuleBuildError'
  }
  at ChildProcess.<anonymous> (lib/next-test-utils.ts:314:11)

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

pnpm test test/integration/client-404/test/index.test.js (turbopack)

  • Auto Export _error bail > production mode > should not opt-out of auto static optimization from invalid _error
Expand output

● Auto Export _error bail › production mode › should not opt-out of auto static optimization from invalid _error

expect(received).toBe(expected) // Object.is equality

Expected: 0
Received: 1

  19 |     const combinedOutput = output.stderr + output.stdout
  20 |
> 21 |     expect(output.code).toBe(0)
     |                         ^
  22 |     expect(combinedOutput).not.toContain(
  23 |       'You have opted-out of Automatic Static Optimization due to'
  24 |     )

  at Object.toBe (integration/auto-export-error-bail/test/index.test.js:21:25)

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

@ijjk
Copy link
Member

ijjk commented Feb 5, 2025

Stats from current PR

Default Build (Increase detected ⚠️)
General
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
buildDuration 15.8s 14.3s N/A
buildDurationCached 13.5s 11.4s N/A
nodeModulesSize 390 MB 390 MB
nextStartRea..uration (ms) 387ms 383ms N/A
Client Bundles (main, webpack) Overall increase ⚠️
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
5306-HASH.js gzip 59.7 kB 60.1 kB ⚠️ +329 B
7048.HASH.js gzip 168 B 168 B
8377-HASH.js gzip 5.48 kB 5.44 kB N/A
bccd1874-HASH.js gzip 53 kB 53 kB
framework-HASH.js gzip 57.3 kB 57.3 kB
main-app-HASH.js gzip 242 B 245 B N/A
main-HASH.js gzip 33.9 kB 33.9 kB N/A
webpack-HASH.js gzip 1.71 kB 1.71 kB
Overall change 172 kB 172 kB ⚠️ +329 B
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js kdy1/issue-72232 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/issue-72232 Change
_app-HASH.js gzip 194 B 194 B
_error-HASH.js gzip 193 B 192 B N/A
amp-HASH.js gzip 516 B 512 B N/A
css-HASH.js gzip 342 B 342 B
dynamic-HASH.js gzip 1.84 kB 1.84 kB N/A
edge-ssr-HASH.js gzip 265 B 264 B N/A
head-HASH.js gzip 359 B 360 B N/A
hooks-HASH.js gzip 392 B 392 B
image-HASH.js gzip 4.58 kB 4.59 kB N/A
index-HASH.js gzip 267 B 265 B N/A
link-HASH.js gzip 2.37 kB 2.37 kB
routerDirect..HASH.js gzip 328 B 327 B N/A
script-HASH.js gzip 396 B 397 B N/A
withRouter-HASH.js gzip 324 B 325 B N/A
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 3.4 kB 3.4 kB
Client Build Manifests
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
_buildManifest.js gzip 753 B 750 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
index.html gzip 523 B 522 B N/A
link.html gzip 539 B 535 B N/A
withRouter.html gzip 520 B 517 B N/A
Overall change 0 B 0 B
Edge SSR bundle Size Overall increase ⚠️
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
edge-ssr.js gzip 133 kB 133 kB N/A
page.js gzip 218 kB 219 kB ⚠️ +1.11 kB
Overall change 218 kB 219 kB ⚠️ +1.11 kB
Middleware size
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
middleware-b..fest.js gzip 677 B 673 B N/A
middleware-r..fest.js gzip 155 B 156 B N/A
middleware.js gzip 31.5 kB 31.3 kB N/A
edge-runtime..pack.js gzip 844 B 844 B
Overall change 844 B 844 B
Next Runtimes
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
app-page-exp...dev.js gzip 376 kB 376 kB
app-page-exp..prod.js gzip 134 kB 134 kB
app-page-tur..prod.js gzip 147 kB 147 kB
app-page-tur..prod.js gzip 142 kB 142 kB
app-page.run...dev.js gzip 365 kB 365 kB
app-page.run..prod.js gzip 130 kB 130 kB
app-route-ex...dev.js gzip 39.5 kB 39.5 kB
app-route-ex..prod.js gzip 25.7 kB 25.7 kB
app-route-tu..prod.js gzip 25.7 kB 25.7 kB
app-route-tu..prod.js gzip 25.5 kB 25.5 kB
app-route.ru...dev.js gzip 39.1 kB 39.1 kB
app-route.ru..prod.js gzip 25.5 kB 25.5 kB
dist_client_...dev.js gzip 356 B 356 B
dist_client_...dev.js gzip 349 B 349 B
pages-api-tu..prod.js gzip 9.74 kB 9.74 kB
pages-api.ru...dev.js gzip 11.8 kB 11.8 kB
pages-api.ru..prod.js gzip 9.74 kB 9.74 kB
pages-turbo...prod.js gzip 22 kB 22 kB
pages.runtim...dev.js gzip 31.6 kB 31.6 kB
pages.runtim..prod.js gzip 22 kB 22 kB
server.runti..prod.js gzip 61.5 kB 61.5 kB
Overall change 1.64 MB 1.64 MB
build cache
vercel/next.js canary vercel/next.js kdy1/issue-72232 Change
0.pack gzip 2.15 MB 2.13 MB N/A
index.pack gzip 76.8 kB 76.8 kB N/A
Overall change 0 B 0 B
Diff details
Diff for page.js

Diff too large to display

Diff for middleware.js

Diff too large to display

Diff for edge-ssr.js

Diff too large to display

Diff for amp-HASH.js
@@ -1,7 +1,34 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [5034],
   {
-    /***/ 2220: /***/ (
+    /***/ 3963: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(9636);
+
+      /***/
+    },
+
+    /***/ 7931: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/amp",
+        function () {
+          return __webpack_require__(8058);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 8058: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -14,7 +41,7 @@
         /* harmony export */
       });
       /* harmony import */ var next_amp__WEBPACK_IMPORTED_MODULE_0__ =
-        __webpack_require__(5061);
+        __webpack_require__(3963);
       /* harmony import */ var next_amp__WEBPACK_IMPORTED_MODULE_0___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_amp__WEBPACK_IMPORTED_MODULE_0__
@@ -32,34 +59,7 @@
       /***/
     },
 
-    /***/ 2705: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/amp",
-        function () {
-          return __webpack_require__(2220);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
-
-    /***/ 5061: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(6188);
-
-      /***/
-    },
-
-    /***/ 6188: /***/ (module, exports, __webpack_require__) => {
+    /***/ 9636: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -75,8 +75,8 @@
       const _react = /*#__PURE__*/ _interop_require_default._(
         __webpack_require__(4109)
       );
-      const _ampcontextsharedruntime = __webpack_require__(5852);
-      const _ampmode = __webpack_require__(9140);
+      const _ampcontextsharedruntime = __webpack_require__(7460);
+      const _ampmode = __webpack_require__(6764);
       function useAmp() {
         // Don't assign the context value to a variable to save bytes
         return (0, _ampmode.isInAmpMode)(
@@ -103,7 +103,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(2705)
+      __webpack_exec__(7931)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for css-HASH.js
@@ -1,7 +1,14 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [9813],
   {
-    /***/ 1487: /***/ (
+    /***/ 408: /***/ (module) => {
+      // extracted by mini-css-extract-plugin
+      module.exports = { helloWorld: "css_helloWorld__aUdUq" };
+
+      /***/
+    },
+
+    /***/ 1313: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -9,7 +16,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/css",
         function () {
-          return __webpack_require__(8037);
+          return __webpack_require__(9559);
         },
       ]);
       if (false) {
@@ -18,14 +25,7 @@
       /***/
     },
 
-    /***/ 7165: /***/ (module) => {
-      // extracted by mini-css-extract-plugin
-      module.exports = { helloWorld: "css_helloWorld__aUdUq" };
-
-      /***/
-    },
-
-    /***/ 8037: /***/ (
+    /***/ 9559: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -39,7 +39,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(8017);
       /* harmony import */ var _css_module_css__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(7165);
+        __webpack_require__(408);
       /* harmony import */ var _css_module_css__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           _css_module_css__WEBPACK_IMPORTED_MODULE_1__
@@ -64,7 +64,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(1487)
+      __webpack_exec__(1313)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for dynamic-HASH.js
@@ -1,24 +1,73 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [2291],
   {
-    /***/ 71: /***/ (
+    /***/ 2253: /***/ (
       __unused_webpack_module,
+      __webpack_exports__,
+      __webpack_require__
+    ) => {
+      "use strict";
+      __webpack_require__.r(__webpack_exports__);
+      /* harmony export */ __webpack_require__.d(__webpack_exports__, {
+        /* harmony export */ __N_SSP: () => /* binding */ __N_SSP,
+        /* harmony export */ default: () => __WEBPACK_DEFAULT_EXPORT__,
+        /* harmony export */
+      });
+      /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
+        __webpack_require__(8017);
+      /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1__ =
+        __webpack_require__(3760);
+      /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1___default =
+        /*#__PURE__*/ __webpack_require__.n(
+          next_dynamic__WEBPACK_IMPORTED_MODULE_1__
+        );
+
+      const DynamicHello = next_dynamic__WEBPACK_IMPORTED_MODULE_1___default()(
+        () =>
+          __webpack_require__
+            .e(/* import() */ 5758)
+            .then(__webpack_require__.bind(__webpack_require__, 5758))
+            .then((mod) => mod.Hello),
+        {
+          loadableGenerated: {
+            webpack: () => [/*require.resolve*/ 5758],
+          },
+        }
+      );
+      const Page = () =>
+        /*#__PURE__*/ (0, react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(
+          react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.Fragment,
+          {
+            children: [
+              /*#__PURE__*/ (0,
+              react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)("p", {
+                children: "testing next/dynamic size",
+              }),
+              /*#__PURE__*/ (0,
+              react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(
+                DynamicHello,
+                {}
+              ),
+            ],
+          }
+        );
+      var __N_SSP = true;
+      /* harmony default export */ const __WEBPACK_DEFAULT_EXPORT__ = Page;
+
+      /***/
+    },
+
+    /***/ 3760: /***/ (
+      module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/dynamic",
-        function () {
-          return __webpack_require__(3487);
-        },
-      ]);
-      if (false) {
-      }
+      module.exports = __webpack_require__(6455);
 
       /***/
     },
 
-    /***/ 2719: /***/ (module, exports, __webpack_require__) => {
+    /***/ 6455: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -51,7 +100,7 @@
         __webpack_require__(4109)
       );
       const _loadablesharedruntime = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(6192)
+        __webpack_require__(9896)
       );
       const isServerSide = "object" === "undefined";
       // Normalize loader to return the module as form { default: Component } for `React.lazy`.
@@ -152,63 +201,7 @@
       /***/
     },
 
-    /***/ 3487: /***/ (
-      __unused_webpack_module,
-      __webpack_exports__,
-      __webpack_require__
-    ) => {
-      "use strict";
-      __webpack_require__.r(__webpack_exports__);
-      /* harmony export */ __webpack_require__.d(__webpack_exports__, {
-        /* harmony export */ __N_SSP: () => /* binding */ __N_SSP,
-        /* harmony export */ default: () => __WEBPACK_DEFAULT_EXPORT__,
-        /* harmony export */
-      });
-      /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
-        __webpack_require__(8017);
-      /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(9330);
-      /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1___default =
-        /*#__PURE__*/ __webpack_require__.n(
-          next_dynamic__WEBPACK_IMPORTED_MODULE_1__
-        );
-
-      const DynamicHello = next_dynamic__WEBPACK_IMPORTED_MODULE_1___default()(
-        () =>
-          __webpack_require__
-            .e(/* import() */ 7048)
-            .then(__webpack_require__.bind(__webpack_require__, 7048))
-            .then((mod) => mod.Hello),
-        {
-          loadableGenerated: {
-            webpack: () => [/*require.resolve*/ 7048],
-          },
-        }
-      );
-      const Page = () =>
-        /*#__PURE__*/ (0, react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)(
-          react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.Fragment,
-          {
-            children: [
-              /*#__PURE__*/ (0,
-              react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)("p", {
-                children: "testing next/dynamic size",
-              }),
-              /*#__PURE__*/ (0,
-              react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(
-                DynamicHello,
-                {}
-              ),
-            ],
-          }
-        );
-      var __N_SSP = true;
-      /* harmony default export */ const __WEBPACK_DEFAULT_EXPORT__ = Page;
-
-      /***/
-    },
-
-    /***/ 5694: /***/ (
+    /***/ 7814: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -235,7 +228,24 @@
       /***/
     },
 
-    /***/ 6192: /***/ (
+    /***/ 8449: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/dynamic",
+        function () {
+          return __webpack_require__(2253);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 9896: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -277,7 +287,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       const _react = /*#__PURE__*/ _interop_require_default._(
         __webpack_require__(4109)
       );
-      const _loadablecontextsharedruntime = __webpack_require__(5694);
+      const _loadablecontextsharedruntime = __webpack_require__(7814);
       function resolve(obj) {
         return obj && obj.default ? obj.default : obj;
       }
@@ -511,23 +521,13 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
 
       /***/
     },
-
-    /***/ 9330: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(2719);
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(71)
+      __webpack_exec__(8449)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for edge-ssr-HASH.js
@@ -1,7 +1,24 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [676],
   {
-    /***/ 1138: /***/ (
+    /***/ 931: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/edge-ssr",
+        function () {
+          return __webpack_require__(9972);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 9972: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -20,30 +37,13 @@
 
       /***/
     },
-
-    /***/ 2673: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/edge-ssr",
-        function () {
-          return __webpack_require__(1138);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(2673)
+      __webpack_exec__(931)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for head-HASH.js
@@ -1,7 +1,24 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [5350],
   {
-    /***/ 4528: /***/ (
+    /***/ 803: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/head",
+        function () {
+          return __webpack_require__(7122);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 7122: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -16,7 +33,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(8017);
       /* harmony import */ var next_head__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(4891);
+        __webpack_require__(9557);
       /* harmony import */ var next_head__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_head__WEBPACK_IMPORTED_MODULE_1__
@@ -50,29 +67,12 @@
       /***/
     },
 
-    /***/ 4891: /***/ (
+    /***/ 9557: /***/ (
       module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(64);
-
-      /***/
-    },
-
-    /***/ 6889: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/head",
-        function () {
-          return __webpack_require__(4528);
-        },
-      ]);
-      if (false) {
-      }
+      module.exports = __webpack_require__(8040);
 
       /***/
     },
@@ -82,7 +82,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(6889)
+      __webpack_exec__(803)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for image-HASH.js
@@ -1,17 +1,96 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [2983],
   {
-    /***/ 1442: /***/ (
+    /***/ 1245: /***/ (
+      __unused_webpack_module,
+      exports,
+      __webpack_require__
+    ) => {
+      "use strict";
+
+      Object.defineProperty(exports, "__esModule", {
+        value: true,
+      });
+      0 && 0;
+      function _export(target, all) {
+        for (var name in all)
+          Object.defineProperty(target, name, {
+            enumerable: true,
+            get: all[name],
+          });
+      }
+      _export(exports, {
+        default: function () {
+          return _default;
+        },
+        getImageProps: function () {
+          return getImageProps;
+        },
+      });
+      const _interop_require_default = __webpack_require__(1532);
+      const _getimgprops = __webpack_require__(6327);
+      const _imagecomponent = __webpack_require__(6003);
+      const _imageloader = /*#__PURE__*/ _interop_require_default._(
+        __webpack_require__(4865)
+      );
+      function getImageProps(imgProps) {
+        const { props } = (0, _getimgprops.getImgProps)(imgProps, {
+          defaultLoader: _imageloader.default,
+          // This is replaced by webpack define plugin
+          imgConf: {
+            deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
+            imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
+            path: "/_next/image",
+            loader: "default",
+            dangerouslyAllowSVG: false,
+            unoptimized: false,
+          },
+        });
+        // Normally we don't care about undefined props because we pass to JSX,
+        // but this exported function could be used by the end user for anything
+        // so we delete undefined props to clean it up a little.
+        for (const [key, value] of Object.entries(props)) {
+          if (value === undefined) {
+            delete props[key];
+          }
+        }
+        return {
+          props,
+        };
+      }
+      const _default = _imagecomponent.Image; //# sourceMappingURL=image-external.js.map
+
+      /***/
+    },
+
+    /***/ 1468: /***/ (
       module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(4549);
+      module.exports = __webpack_require__(1245);
+
+      /***/
+    },
+
+    /***/ 1989: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/image",
+        function () {
+          return __webpack_require__(8136);
+        },
+      ]);
+      if (false) {
+      }
 
       /***/
     },
 
-    /***/ 3582: /***/ (module, exports, __webpack_require__) => {
+    /***/ 3942: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -89,116 +168,7 @@
       /***/
     },
 
-    /***/ 4549: /***/ (
-      __unused_webpack_module,
-      exports,
-      __webpack_require__
-    ) => {
-      "use strict";
-
-      Object.defineProperty(exports, "__esModule", {
-        value: true,
-      });
-      0 && 0;
-      function _export(target, all) {
-        for (var name in all)
-          Object.defineProperty(target, name, {
-            enumerable: true,
-            get: all[name],
-          });
-      }
-      _export(exports, {
-        default: function () {
-          return _default;
-        },
-        getImageProps: function () {
-          return getImageProps;
-        },
-      });
-      const _interop_require_default = __webpack_require__(1532);
-      const _getimgprops = __webpack_require__(8831);
-      const _imagecomponent = __webpack_require__(7739);
-      const _imageloader = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(4777)
-      );
-      function getImageProps(imgProps) {
-        const { props } = (0, _getimgprops.getImgProps)(imgProps, {
-          defaultLoader: _imageloader.default,
-          // This is replaced by webpack define plugin
-          imgConf: {
-            deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
-            imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
-            path: "/_next/image",
-            loader: "default",
-            dangerouslyAllowSVG: false,
-            unoptimized: false,
-          },
-        });
-        // Normally we don't care about undefined props because we pass to JSX,
-        // but this exported function could be used by the end user for anything
-        // so we delete undefined props to clean it up a little.
-        for (const [key, value] of Object.entries(props)) {
-          if (value === undefined) {
-            delete props[key];
-          }
-        }
-        return {
-          props,
-        };
-      }
-      const _default = _imagecomponent.Image; //# sourceMappingURL=image-external.js.map
-
-      /***/
-    },
-
-    /***/ 4777: /***/ (__unused_webpack_module, exports) => {
-      "use strict";
-
-      Object.defineProperty(exports, "__esModule", {
-        value: true,
-      });
-      Object.defineProperty(exports, "default", {
-        enumerable: true,
-        get: function () {
-          return _default;
-        },
-      });
-      const DEFAULT_Q = 75;
-      function defaultLoader(param) {
-        let { config, src, width, quality } = param;
-        var _config_qualities;
-        if (false) {
-        }
-        const q =
-          quality ||
-          ((_config_qualities = config.qualities) == null
-            ? void 0
-            : _config_qualities.reduce((prev, cur) =>
-                Math.abs(cur - DEFAULT_Q) < Math.abs(prev - DEFAULT_Q)
-                  ? cur
-                  : prev
-              )) ||
-          DEFAULT_Q;
-        return (
-          config.path +
-          "?url=" +
-          encodeURIComponent(src) +
-          "&w=" +
-          width +
-          "&q=" +
-          q +
-          (src.startsWith("/_next/static/media/") && false ? 0 : "")
-        );
-      }
-      // We use this to determine if the import is the default loader
-      // or a custom loader defined by the user in next.config.js
-      defaultLoader.__next_img_default = true;
-      const _default = defaultLoader; //# sourceMappingURL=image-loader.js.map
-
-      /***/
-    },
-
-    /***/ 5328: /***/ (__unused_webpack_module, exports) => {
+    /***/ 4328: /***/ (__unused_webpack_module, exports) => {
       "use strict";
       /**
        * A shared function, used on both client and server, to generate a SVG blur placeholder.
@@ -253,24 +223,54 @@
       /***/
     },
 
-    /***/ 6923: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/image",
-        function () {
-          return __webpack_require__(8964);
+    /***/ 4865: /***/ (__unused_webpack_module, exports) => {
+      "use strict";
+
+      Object.defineProperty(exports, "__esModule", {
+        value: true,
+      });
+      Object.defineProperty(exports, "default", {
+        enumerable: true,
+        get: function () {
+          return _default;
         },
-      ]);
-      if (false) {
+      });
+      const DEFAULT_Q = 75;
+      function defaultLoader(param) {
+        let { config, src, width, quality } = param;
+        var _config_qualities;
+        if (false) {
+        }
+        const q =
+          quality ||
+          ((_config_qualities = config.qualities) == null
+            ? void 0
+            : _config_qualities.reduce((prev, cur) =>
+                Math.abs(cur - DEFAULT_Q) < Math.abs(prev - DEFAULT_Q)
+                  ? cur
+                  : prev
+              )) ||
+          DEFAULT_Q;
+        return (
+          config.path +
+          "?url=" +
+          encodeURIComponent(src) +
+          "&w=" +
+          width +
+          "&q=" +
+          q +
+          (src.startsWith("/_next/static/media/") && false ? 0 : "")
+        );
       }
+      // We use this to determine if the import is the default loader
+      // or a custom loader defined by the user in next.config.js
+      defaultLoader.__next_img_default = true;
+      const _default = defaultLoader; //# sourceMappingURL=image-loader.js.map
 
       /***/
     },
 
-    /***/ 7739: /***/ (module, exports, __webpack_require__) => {
+    /***/ 6003: /***/ (module, exports, __webpack_require__) => {
       "use strict";
       /* __next_internal_client_entry_do_not_use__  cjs */
       Object.defineProperty(exports, "__esModule", {
@@ -292,17 +292,17 @@
         __webpack_require__(5775)
       );
       const _head = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(64)
+        __webpack_require__(8040)
       );
-      const _getimgprops = __webpack_require__(8831);
-      const _imageconfig = __webpack_require__(1839);
-      const _imageconfigcontextsharedruntime = __webpack_require__(1516);
-      const _warnonce = __webpack_require__(4814);
-      const _routercontextsharedruntime = __webpack_require__(3245);
+      const _getimgprops = __webpack_require__(6327);
+      const _imageconfig = __webpack_require__(4740);
+      const _imageconfigcontextsharedruntime = __webpack_require__(9764);
+      const _warnonce = __webpack_require__(8310);
+      const _routercontextsharedruntime = __webpack_require__(3061);
       const _imageloader = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(4777)
+        __webpack_require__(4865)
       );
-      const _usemergedref = __webpack_require__(3582);
+      const _usemergedref = __webpack_require__(3942);
       // This is replaced by webpack define plugin
       const configEnv = {
         deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
@@ -629,7 +629,7 @@
       /***/
     },
 
-    /***/ 8831: /***/ (
+    /***/ 6327: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -645,9 +645,9 @@
           return getImgProps;
         },
       });
-      const _warnonce = __webpack_require__(4814);
-      const _imageblursvg = __webpack_require__(5328);
-      const _imageconfig = __webpack_require__(1839);
+      const _warnonce = __webpack_require__(8310);
+      const _imageblursvg = __webpack_require__(4328);
+      const _imageconfig = __webpack_require__(4740);
       const VALID_LOADING_VALUES =
         /* unused pure expression or super */ null && [
           "lazy",
@@ -1059,7 +1059,7 @@
       /***/
     },
 
-    /***/ 8964: /***/ (
+    /***/ 8136: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -1076,8 +1076,8 @@
 
       // EXTERNAL MODULE: ./node_modules/.pnpm/react@19.0.0/node_modules/react/jsx-runtime.js
       var jsx_runtime = __webpack_require__(8017);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+main-repo+packages+next+next-packed.tgz_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/image.js
-      var next_image = __webpack_require__(1442);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@file+..+diff-repo+packages+next+next-packed.tgz_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/image.js
+      var next_image = __webpack_require__(1468);
       var image_default = /*#__PURE__*/ __webpack_require__.n(next_image); // ./pages/nextjs.png
       /* harmony default export */ const nextjs = {
         src: "/_next/static/media/nextjs.cae0b805.png",
@@ -1112,7 +1112,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(6923)
+      __webpack_exec__(1989)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for link-HASH.js
@@ -1,7 +1,102 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [4672],
   {
-    /***/ 1368: /***/ (module, exports, __webpack_require__) => {
+    /***/ 1547: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/link",
+        function () {
+          return __webpack_require__(5944);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 3942: /***/ (module, exports, __webpack_require__) => {
+      "use strict";
+
+      Object.defineProperty(exports, "__esModule", {
+        value: true,
+      });
+      Object.defineProperty(exports, "useMergedRef", {
+        enumerable: true,
+        get: function () {
+          return useMergedRef;
+        },
+      });
+      const _react = __webpack_require__(4109);
+      function useMergedRef(refA, refB) {
+        const cleanupA = (0, _react.useRef)(null);
+        const cleanupB = (0, _react.useRef)(null);
+        // NOTE: In theory, we could skip the wrapping if only one of the refs is non-null.
+        // (this happens often if the user doesn't pass a ref to Link/Form/Image)
+        // But this can cause us to leak a cleanup-ref into user code (e.g. via `<Link legacyBehavior>`),
+        // and the user might pass that ref into ref-merging library that doesn't support cleanup refs
+        // (because it hasn't been updated for React 19)
+        // which can then cause things to blow up, because a cleanup-returning ref gets called with `null`.
+        // So in practice, it's safer to be defensive and always wrap the ref, even on React 19.
+        return (0, _react.useCallback)(
+          (current) => {
+            if (current === null) {
+              const cleanupFnA = cleanupA.current;
+              if (cleanupFnA) {
+                cleanupA.current = null;
+                cleanupFnA();
+              }
+              const cleanupFnB = cleanupB.current;
+              if (cleanupFnB) {
+                cleanupB.current = null;
+                cleanupFnB();
+              }
+            } else {
+              if (refA) {
+                cleanupA.current = applyRef(refA, current);
+              }
+              if (refB) {
+                cleanupB.current = applyRef(refB, current);
+              }
+            }
+          },
+          [refA, refB]
+        );
+      }
+      function applyRef(refA, current) {
+        if (typeof refA === "function") {
+          const cleanup = refA(current);
+          if (typeof cleanup === "function") {
+            return cleanup;
+          } else {
+            return () => refA(null);
+          }
+        } else {
+          refA.current = current;
+          return () => {
+            refA.current = null;
+          };
+        }
+      }
+      if (
+        (typeof exports.default === "function" ||
+          (typeof exports.default === "object" && exports.default !== null)) &&
+        typeof exports.default.__esModule === "undefined"
+      ) {
+        Object.defineProperty(exports.default, "__esModule", {
+          value: true,
+        });
+        Object.assign(exports.default, exports);
+        module.exports = exports.default;
+      } //# sourceMappingURL=use-merged-ref.js.map
+
+      /***/
+    },
+
+    /***/ 4144: /***/ (module, exports, __webpack_require__) => {
       "use strict";
       /* __next_internal_client_entry_do_not_use__  cjs */
       Object.defineProperty(exports, "__esModule", {
@@ -18,16 +113,16 @@
       const _react = /*#__PURE__*/ _interop_require_default._(
         __webpack_require__(4109)
       );
-      const _resolvehref = __webpack_require__(1462);
-      const _islocalurl = __webpack_require__(3876);
-      const _formaturl = __webpack_require__(1389);
-      const _utils = __webpack_require__(3675);
-      const _addlocale = __webpack_require__(4452);
-      const _routercontextsharedruntime = __webpack_require__(3245);
-      const _useintersection = __webpack_require__(8587);
-      const _getdomainlocale = __webpack_require__(2528);
-      const _addbasepath = __webpack_require__(6921);
-      const _usemergedref = __webpack_require__(3582);
+      const _resolvehref = __webpack_require__(3358);
+      const _islocalurl = __webpack_require__(2220);
+      const _formaturl = __webpack_require__(5653);
+      const _utils = __webpack_require__(3699);
+      const _addlocale = __webpack_require__(7980);
+      const _routercontextsharedruntime = __webpack_require__(3061);
+      const _useintersection = __webpack_require__(8835);
+      const _getdomainlocale = __webpack_require__(4552);
+      const _addbasepath = __webpack_require__(8353);
+      const _usemergedref = __webpack_require__(3942);
       const prefetched = new Set();
       function prefetch(router, href, as, options) {
         if (false) {
@@ -380,7 +475,7 @@
       /***/
     },
 
-    /***/ 2528: /***/ (module, exports, __webpack_require__) => {
+    /***/ 4552: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -392,7 +487,7 @@
           return getDomainLocale;
         },
       });
-      const _normalizetrailingslash = __webpack_require__(3894);
+      const _normalizetrailingslash = __webpack_require__(7758);
       const basePath =
         /* unused pure expression or super */ null && (false || "");
       function getDomainLocale(path, locale, locales, domainLocales) {
@@ -416,112 +511,53 @@
       /***/
     },
 
-    /***/ 2665: /***/ (
-      module,
-      __unused_webpack_exports,
+    /***/ 5944: /***/ (
+      __unused_webpack_module,
+      __webpack_exports__,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(1368);
-
-      /***/
-    },
-
-    /***/ 3582: /***/ (module, exports, __webpack_require__) => {
       "use strict";
-
-      Object.defineProperty(exports, "__esModule", {
-        value: true,
-      });
-      Object.defineProperty(exports, "useMergedRef", {
-        enumerable: true,
-        get: function () {
-          return useMergedRef;
-        },
+      __webpack_require__.r(__webpack_exports__);
+      /* harmony export */ __webpack_require__.d(__webpack_exports__, {
+        /* harmony export */ __N_SSP: () => /* binding */ __N_SSP,
+        /* harmony export */ default: () => __WEBPACK_DEFAULT_EXPORT__,
+        /* harmony export */
       });
-      const _react = __webpack_require__(4109);
-      function useMergedRef(refA, refB) {
-        const cleanupA = (0, _react.useRef)(null);
-        const cleanupB = (0, _react.useRef)(null);
-        // NOTE: In theory, we could skip the wrapping if only one of the refs is non-null.
-        // (this happens often if the user doesn't pass a ref to Link/Form/Image)
-        // But this can cause us to leak a cleanup-ref into user code (e.g. via `<Link legacyBehavior>`),
-        // and the user might pass that ref into ref-merging library that doesn't support cleanup refs
-        // (because it hasn't been updated for React 19)
-        // which can then cause things to blow up, because a cleanup-returning ref gets called with `null`.
-        // So in practice, it's safer to be defensive and always wrap the ref, even on React 19.
-        return (0, _react.useCallback)(
-          (current) => {
-            if (current === null) {
-              const cleanupFnA = cleanupA.current;
-              if (cleanupFnA) {
-                cleanupA.current = null;
-                cleanupFnA();
-              }
-              const cleanupFnB = cleanupB.current;
-              if (cleanupFnB) {
-                cleanupB.current = null;
-                cleanupFnB();
-              }
-            } else {
-              if (refA) {
-                cleanupA.current = applyRef(refA, current);
-              }
-              if (refB) {
-                cleanupB.current = applyRef(refB, current);
-              }
-            }
-          },
-          [refA, refB]
+      /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
+        __webpack_require__(8017);
+      /* harmony import */ var next_link__WEBPACK_IMPORTED_MODULE_1__ =
+        __webpack_require__(9835);
+      /* harmony import */ var next_link__WEBPACK_IMPORTED_MODULE_1___default =
+        /*#__PURE__*/ __webpack_require__.n(
+          next_link__WEBPACK_IMPORTED_MODULE_1__
         );
-      }
-      function applyRef(refA, current) {
-        if (typeof refA === "function") {
-          const cleanup = refA(current);
-          if (typeof cleanup === "function") {
-            return cleanup;
-          } else {
-            return () => refA(null);
-          }
-        } else {
-          refA.current = current;
-          return () => {
-            refA.current = null;
-          };
-        }
-      }
-      if (
-        (typeof exports.default === "function" ||
-          (typeof exports.default === "object" && exports.default !== null)) &&
-        typeof exports.default.__esModule === "undefined"
-      ) {
-        Object.defineProperty(exports.default, "__esModule", {
-          value: true,
-        });
-        Object.assign(exports.default, exports);
-        module.exports = exports.default;
-      } //# sourceMappingURL=use-merged-ref.js.map
-
-      /***/
-    },
 
-    /***/ 5025: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/link",
-        function () {
-          return __webpack_require__(9718);
-        },
-      ]);
-      if (false) {
+      function aLink(props) {
+        return /*#__PURE__*/ (0,
+        react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)("div", {
+          children: [
+            /*#__PURE__*/ (0,
+            react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)("h3", {
+              children: "A Link page!",
+            }),
+            /*#__PURE__*/ (0,
+            react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(
+              next_link__WEBPACK_IMPORTED_MODULE_1___default(),
+              {
+                href: "/",
+                children: "Go to /",
+              }
+            ),
+          ],
+        });
       }
+      var __N_SSP = true;
+      /* harmony default export */ const __WEBPACK_DEFAULT_EXPORT__ = aLink;
 
       /***/
     },
 
-    /***/ 8587: /***/ (module, exports, __webpack_require__) => {
+    /***/ 8835: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -534,7 +570,7 @@
         },
       });
       const _react = __webpack_require__(4109);
-      const _requestidlecallback = __webpack_require__(902);
+      const _requestidlecallback = __webpack_require__(6190);
       const hasIntersectionObserver =
         typeof IntersectionObserver === "function";
       const observers = new Map();
@@ -647,48 +683,12 @@
       /***/
     },
 
-    /***/ 9718: /***/ (
-      __unused_webpack_module,
-      __webpack_exports__,
+    /***/ 9835: /***/ (
+      module,
+      __unused_webpack_exports,
       __webpack_require__
     ) => {
-      "use strict";
-      __webpack_require__.r(__webpack_exports__);
-      /* harmony export */ __webpack_require__.d(__webpack_exports__, {
-        /* harmony export */ __N_SSP: () => /* binding */ __N_SSP,
-        /* harmony export */ default: () => __WEBPACK_DEFAULT_EXPORT__,
-        /* harmony export */
-      });
-      /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
-        __webpack_require__(8017);
-      /* harmony import */ var next_link__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(2665);
-      /* harmony import */ var next_link__WEBPACK_IMPORTED_MODULE_1___default =
-        /*#__PURE__*/ __webpack_require__.n(
-          next_link__WEBPACK_IMPORTED_MODULE_1__
-        );
-
-      function aLink(props) {
-        return /*#__PURE__*/ (0,
-        react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxs)("div", {
-          children: [
-            /*#__PURE__*/ (0,
-            react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)("h3", {
-              children: "A Link page!",
-            }),
-            /*#__PURE__*/ (0,
-            react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(
-              next_link__WEBPACK_IMPORTED_MODULE_1___default(),
-              {
-                href: "/",
-                children: "Go to /",
-              }
-            ),
-          ],
-        });
-      }
-      var __N_SSP = true;
-      /* harmony default export */ const __WEBPACK_DEFAULT_EXPORT__ = aLink;
+      module.exports = __webpack_require__(4144);
 
       /***/
     },
@@ -698,7 +698,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(5025)
+      __webpack_exec__(1547)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for routerDirect-HASH.js
@@ -1,17 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [188],
   {
-    /***/ 760: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(1841);
-
-      /***/
-    },
-
-    /***/ 2713: /***/ (
+    /***/ 179: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -19,7 +9,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/routerDirect",
         function () {
-          return __webpack_require__(4077);
+          return __webpack_require__(7216);
         },
       ]);
       if (false) {
@@ -28,7 +18,17 @@
       /***/
     },
 
-    /***/ 4077: /***/ (
+    /***/ 3022: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(1177);
+
+      /***/
+    },
+
+    /***/ 7216: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -43,7 +43,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(8017);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(760);
+        __webpack_require__(3022);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_router__WEBPACK_IMPORTED_MODULE_1__
@@ -68,7 +68,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(2713)
+      __webpack_exec__(179)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for script-HASH.js
@@ -1,34 +1,17 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [1209],
   {
-    /***/ 3254: /***/ (
+    /***/ 1060: /***/ (
       module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(8807);
+      module.exports = __webpack_require__(9599);
 
       /***/
     },
 
-    /***/ 8745: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/script",
-        function () {
-          return __webpack_require__(8913);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
-
-    /***/ 8913: /***/ (
+    /***/ 1815: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -43,7 +26,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(8017);
       /* harmony import */ var next_script__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(3254);
+        __webpack_require__(1060);
       /* harmony import */ var next_script__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_script__WEBPACK_IMPORTED_MODULE_1__
@@ -75,13 +58,30 @@
 
       /***/
     },
+
+    /***/ 5867: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/script",
+        function () {
+          return __webpack_require__(1815);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(8745)
+      __webpack_exec__(5867)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for withRouter-HASH.js
@@ -1,17 +1,34 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [3263],
   {
-    /***/ 760: /***/ (
+    /***/ 3022: /***/ (
       module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(1841);
+      module.exports = __webpack_require__(1177);
 
       /***/
     },
 
-    /***/ 2867: /***/ (
+    /***/ 4563: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/withRouter",
+        function () {
+          return __webpack_require__(6490);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 6490: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -26,7 +43,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(8017);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(760);
+        __webpack_require__(3022);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_router__WEBPACK_IMPORTED_MODULE_1__
@@ -44,30 +61,13 @@
 
       /***/
     },
-
-    /***/ 6545: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/withRouter",
-        function () {
-          return __webpack_require__(2867);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(6545)
+      __webpack_exec__(4563)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for 5306-HASH.js
failed to diff
Diff for 8377-HASH.js

Diff too large to display

Diff for main-HASH.js

Diff too large to display

Commit: ba088e4

@@ -429,6 +430,7 @@ async fn emit_star_exports_issue(source_ident: Vc<AssetIdent>, message: RcStr) -
#[turbo_tasks::value(shared)]
#[derive(Hash, Debug)]
pub struct EsmExports {
pub parsed: ResolvedVc<ParseResult>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of storing that here, we should instead pass the ParseResult to code_generation

@kdy1 kdy1 marked this pull request as draft February 5, 2025 04:04
@kdy1 kdy1 requested a review from sokra February 25, 2025 09:08
@kdy1 kdy1 marked this pull request as ready for review February 25, 2025 09:08
kdy1 and others added 2 commits February 28, 2025 09:34
…t.rs

Co-authored-by: Benjamin Woodruff <benjamin.woodruff@vercel.com>
…t.rs

Co-authored-by: Benjamin Woodruff <benjamin.woodruff@vercel.com>
@kdy1 kdy1 enabled auto-merge (squash) February 28, 2025 00:35
@kdy1 kdy1 marked this pull request as draft February 28, 2025 01:39
auto-merge was automatically disabled February 28, 2025 01:39

Pull request was converted to draft

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. Turbopack Related to Turbopack with Next.js.
Projects
None yet
7 participants