Skip to content

[dev-tools] display metadata object #79547

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

Draft
wants to merge 3 commits into
base: jiwon/05-22-_dev-tools_initial_support_for_viewing_static_params_of_current_route_from_generatestaticparams_
Choose a base branch
from

Conversation

devjiwonchoi
Copy link
Member

No description provided.

Copy link

changeset-bot bot commented May 23, 2025

⚠️ No Changeset found

Latest commit: 792df26

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Member Author

devjiwonchoi commented May 23, 2025

@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-22-_dev-tools_initial_support_for_viewing_static_params_of_current_route_from_generatestaticparams_ branch from 0c6a219 to bf72941 Compare May 23, 2025 14:21
@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-23-_dev-tools_display_metadata_object branch 2 times, most recently from 40bc082 to c7f4203 Compare May 23, 2025 14:40
@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-22-_dev-tools_initial_support_for_viewing_static_params_of_current_route_from_generatestaticparams_ branch 2 times, most recently from 609d59c to aee1dbb Compare May 23, 2025 16:54
@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-23-_dev-tools_display_metadata_object branch from c7f4203 to a6706a7 Compare May 23, 2025 16:54
@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-23-_dev-tools_display_metadata_object branch from a6706a7 to e8da517 Compare May 23, 2025 17:17
@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-23-_dev-tools_display_metadata_object branch from e8da517 to a2dc5d1 Compare May 23, 2025 17:54
@devjiwonchoi devjiwonchoi force-pushed the jiwon/05-22-_dev-tools_initial_support_for_viewing_static_params_of_current_route_from_generatestaticparams_ branch from 07251df to 35f5a4a Compare May 23, 2025 17:54
@ijjk ijjk added the Rspack label May 23, 2025
@ijjk
Copy link
Member

ijjk commented May 23, 2025

Failing test suites

Commit: 792df26

pnpm test test/integration/app-dir-export/test/start.test.ts

  • app dir - with output export (next start) > production mode > should error during next start with output export
Expand output

● app dir - with output export (next start) › production mode › should error during next start with output export

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
 ✓ Compiled successfully in 3.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/13) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/image-import". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '1011690433'
}
Export encountered an error on /image-import/page: /image-import, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

  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/app-dir-export/test/config.test.ts

  • app dir - with output export (next dev / next build) > production mode > should error when running next export
  • app dir - with output export (next dev / next build) > production mode > should correctly emit exported assets to config.distDir
Expand output

● app dir - with output export (next dev / next build) › production mode › should error when running next export

command failed with code 1 signal null
 ⚠ Linting is disabled.
   No config file found
   No config file found
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   No config file found
   No config file found
   No config file found
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/13) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/image-import". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '1011690433'
}
Export encountered an error on /image-import/page: /image-import, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● app dir - with output export (next dev / next build) › production mode › should correctly emit exported assets to config.distDir

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/app-dir-export/next.config.js
 ✓ Compiled successfully in 3.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/13) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/another/second". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2061103402'
}
Export encountered an error on /another/[slug]/page: /another/second, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

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

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

  • app-dir action disallowed origins > should error if x-forwarded-host does not match the origin
Expand output

● app-dir action disallowed origins › should error if x-forwarded-host does not match the origin

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-prefetch-static/app-prefetch-static.test.ts (turbopack)

  • app-prefetch-static > should correctly navigate between static & dynamic pages
Expand output

● app-prefetch-static › should correctly navigate between static & dynamic pages

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 test/e2e/app-dir/app-catch-all-optional/app-catch-all-optional.test.ts

  • app-catch-all-optional > should handle optional catchall
  • app-catch-all-optional > should handle optional catchall with no params
Expand output

● app-catch-all-optional › should handle optional catchall

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-catch-all-optional › should handle optional catchall with no params

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/next-image-new/app-dir/test/index.test.ts (turbopack)

  • Image Component Default Tests > production mode > should load the images
  • Image Component Default Tests > production mode > should preload priority images
  • Image Component Default Tests > production mode > should not pass through user-provided srcset (causing a flash)
  • Image Component Default Tests > production mode > should update the image on src change
  • Image Component Default Tests > production mode > should callback onLoadingComplete when image is fully loaded
  • Image Component Default Tests > production mode > should callback native onLoad with sythetic event
  • Image Component Default Tests > production mode > should callback native onError when error occurred while loading image
  • Image Component Default Tests > production mode > should callback native onError even when error before hydration
  • Image Component Default Tests > production mode > should work with image with blob src
  • Image Component Default Tests > production mode > should work when using flexbox
  • Image Component Default Tests > production mode > should work when using overrideSrc prop
  • Image Component Default Tests > production mode > should work with sizes and automatically use responsive srcset
  • Image Component Default Tests > production mode > should render no wrappers or sizers
  • Image Component Default Tests > production mode > should lazy load with placeholder=blur
  • Image Component Default Tests > production mode > should handle the styles prop appropriately
  • Image Component Default Tests > production mode > should warn when legacy prop layout=fill
  • Image Component Default Tests > production mode > should warn when legacy prop layout=responsive
  • Image Component Default Tests > production mode > should render picture via getImageProps
  • Image Component Default Tests > production mode > should not create an image folder in server/chunks
  • Image Component Default Tests > production mode > should render as unoptimized with missing src prop
  • Image Component Default Tests > production mode > should render as unoptimized with empty string src prop
  • Image Component Default Tests > production mode > should correctly ignore prose styles
  • Image Component Default Tests > production mode > should apply style inheritance for img elements but not wrapper elements
  • Image Component Default Tests > production mode > should apply filter style after image loads
  • Image Component Default Tests > production mode > should emit image for next/dynamic with non ssr case
  • Image Component Default Tests > production mode > should correctly rotate image
  • Image Component Default Tests > production mode > should have data url placeholder when enabled
  • Image Component Default Tests > production mode > should remove data url placeholder after image loads
  • Image Component Default Tests > production mode > should render correct objectFit when data url placeholder and fill
  • Image Component Default Tests > production mode > should have blurry placeholder when enabled
  • Image Component Default Tests > production mode > should remove blurry placeholder after image loads
  • Image Component Default Tests > production mode > should render correct objectFit when blurDataURL and fill
  • Image Component Default Tests > production mode > should be valid HTML
  • Image Component Default Tests > production mode > should call callback ref cleanups when unmounting
  • Image Component Default Tests > production mode > should build correct images-manifest.json
  • Image Component Default Tests > production mode > Fill-mode tests > should include a data-attribute on fill images
  • Image Component Default Tests > production mode > Fill-mode tests > should add position:absolute to fill images
  • Image Component Default Tests > production mode > Fill-mode tests > should add 100% width and height to fill images
  • Image Component Default Tests > production mode > Fill-mode tests > should add position styles to fill images
Expand output

● Image Component Default Tests › production mode › should load the images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should preload priority images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should not pass through user-provided srcset (causing a flash)

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should update the image on src change

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should callback onLoadingComplete when image is fully loaded

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should callback native onLoad with sythetic event

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should callback native onError when error occurred while loading image

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should callback native onError even when error before hydration

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should work with image with blob src

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should work when using flexbox

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should work when using overrideSrc prop

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should work with sizes and automatically use responsive srcset

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should render no wrappers or sizers

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should lazy load with placeholder=blur

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should handle the styles prop appropriately

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should warn when legacy prop layout=fill

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should warn when legacy prop layout=responsive

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should render picture via getImageProps

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should not create an image folder in server/chunks

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should render as unoptimized with missing src prop

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should render as unoptimized with empty string src prop

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should correctly ignore prose styles

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should apply style inheritance for img elements but not wrapper elements

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should apply filter style after image loads

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should emit image for next/dynamic with non ssr case

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › Fill-mode tests › should include a data-attribute on fill images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › Fill-mode tests › should include a data-attribute on fill images

page.goto: Protocol error (Page.navigate): Cannot navigate to invalid URL
Call log:
  - navigating to "http://localhost:undefined/fill", waiting until "load"

  313 |     opts?.beforePageLoad?.(page)
  314 |
> 315 |     await page.goto(url, { waitUntil: 'load' })
      |                ^
  316 |   }
  317 |
  318 |   back(options?: Parameters<Page['goBack']>[0]) {

  at Playwright.goto (lib/browsers/playwright.ts:315:16)
  at webdriver (lib/next-webdriver.ts:143:3)
  at Object.<anonymous> (integration/next-image-new/app-dir/test/index.test.ts:1335:17)

● Image Component Default Tests › production mode › Fill-mode tests › should add position:absolute to fill images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › Fill-mode tests › should add position:absolute to fill images

page.goto: Protocol error (Page.navigate): Cannot navigate to invalid URL
Call log:
  - navigating to "http://localhost:undefined/fill", waiting until "load"

  313 |     opts?.beforePageLoad?.(page)
  314 |
> 315 |     await page.goto(url, { waitUntil: 'load' })
      |                ^
  316 |   }
  317 |
  318 |   back(options?: Parameters<Page['goBack']>[0]) {

  at Playwright.goto (lib/browsers/playwright.ts:315:16)
  at webdriver (lib/next-webdriver.ts:143:3)
  at Object.<anonymous> (integration/next-image-new/app-dir/test/index.test.ts:1335:17)

● Image Component Default Tests › production mode › Fill-mode tests › should add 100% width and height to fill images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › Fill-mode tests › should add 100% width and height to fill images

page.goto: Protocol error (Page.navigate): Cannot navigate to invalid URL
Call log:
  - navigating to "http://localhost:undefined/fill", waiting until "load"

  313 |     opts?.beforePageLoad?.(page)
  314 |
> 315 |     await page.goto(url, { waitUntil: 'load' })
      |                ^
  316 |   }
  317 |
  318 |   back(options?: Parameters<Page['goBack']>[0]) {

  at Playwright.goto (lib/browsers/playwright.ts:315:16)
  at webdriver (lib/next-webdriver.ts:143:3)
  at Object.<anonymous> (integration/next-image-new/app-dir/test/index.test.ts:1335:17)

● Image Component Default Tests › production mode › Fill-mode tests › should add position styles to fill images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › Fill-mode tests › should add position styles to fill images

page.goto: Protocol error (Page.navigate): Cannot navigate to invalid URL
Call log:
  - navigating to "http://localhost:undefined/fill", waiting until "load"

  313 |     opts?.beforePageLoad?.(page)
  314 |
> 315 |     await page.goto(url, { waitUntil: 'load' })
      |                ^
  316 |   }
  317 |
  318 |   back(options?: Parameters<Page['goBack']>[0]) {

  at Playwright.goto (lib/browsers/playwright.ts:315:16)
  at webdriver (lib/next-webdriver.ts:143:3)
  at Object.<anonymous> (integration/next-image-new/app-dir/test/index.test.ts:1335:17)

● Image Component Default Tests › production mode › should correctly rotate image

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should have data url placeholder when enabled

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should remove data url placeholder after image loads

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should render correct objectFit when data url placeholder and fill

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should have blurry placeholder when enabled

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should remove blurry placeholder after image loads

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should render correct objectFit when blurDataURL and fill

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should be valid HTML

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should call callback ref cleanups when unmounting

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image Component Default Tests › production mode › should build correct images-manifest.json

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 68.19708ms
Turbopack build encountered 1 warnings:
./test/integration/next-image-new/app-dir/public/test.avif
AVIF image not supported
This version of Turbopack does not support AVIF images, will emit without optimization or encoding


 ✓ Compiled successfully in 3.9s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/61) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/rotated". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2671340172'
}
Export encountered an error on /rotated/page: /rotated, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-start test/e2e/app-dir/actions-navigation/index.test.ts (PPR)

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

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

next build failed with code/signal 1

  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 action handling › should handle actions correctly after following a relative link

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 test/e2e/app-dir/app-rendering/rendering.test.ts

  • app dir rendering > should serve app/page.server.js at /
  • app dir rendering > ISR > should revalidate the page when revalidate is configured
  • app dir rendering > SSR only > should run data in layout and page
  • app dir rendering > SSR only > should run data fetch in parallel
  • app dir rendering > static only > should run data in layout and page
  • app dir rendering > static only > should run data in parallel and use cached version for production
Expand output

● app dir rendering › should serve app/page.server.js at /

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 rendering › SSR only › should run data in layout and page

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 rendering › SSR only › should run data fetch in parallel

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 rendering › static only › should run data in layout and page

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 rendering › static only › should run data in parallel and use cached version for production

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 rendering › ISR › should revalidate the page when revalidate is configured

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 rendering › mixed static and dynamic › should generate static data during build and use it

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/actions-allowed-origins/app-action-allowed-origins.test.ts (turbopack)

  • app-dir action allowed origins > should pass if localhost is set as a safe origin
Expand output

● app-dir action allowed origins › should pass if localhost is set as a safe origin

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-inline-css/index.test.ts (turbopack)

  • app dir - css - experimental inline css > Production only > should render page with correct styles
  • app dir - css - experimental inline css > Production only > should not return rsc payload with inlined style as a dynamic client nav
  • app dir - css - experimental inline css > Production only > should have only one style tag when navigating from page with inlining to page without inlining
Expand output

● app dir - css - experimental inline css › Production only › should render page with correct styles

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 - css - experimental inline css › Production only › should not return rsc payload with inlined style as a dynamic client nav

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 - css - experimental inline css › Production only › should have only one style tag when navigating from page with inlining to page without inlining

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 test/e2e/app-dir/app-css-pageextensions/index.test.ts

  • app dir - css with pageextensions > css support with pageextensions > page in app directory with pageextention, css should work > should support global css inside layout
Expand output

● app dir - css with pageextensions › css support with pageextensions › page in app directory with pageextention, css should work › should support global css inside layout

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 test/e2e/app-dir/app-config-crossorigin/index.test.ts

  • app dir - crossOrigin config > skip in start mode
Expand output

● app dir - crossOrigin config › skip in start mode

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.

__NEXT_EXPERIMENTAL_PPR=true pnpm test-start test/e2e/app-dir/asset-prefix-with-basepath/asset-prefix-with-basepath.test.ts (PPR)

  • app-dir assetPrefix with basePath handling > should redirect route when requesting it directly
  • app-dir assetPrefix with basePath handling > should render link
  • app-dir assetPrefix with basePath handling > should redirect route when requesting it directly by browser
  • app-dir assetPrefix with basePath handling > should redirect route when clicking link
  • app-dir assetPrefix with basePath handling > bundles should return 200 on served assetPrefix
  • app-dir assetPrefix with basePath handling > rewrites > rewrites that do not start with assetPrefix should still work
  • app-dir assetPrefix with basePath handling > rewrites > should respect rewrites that start with assetPrefix
Expand output

● app-dir assetPrefix with basePath handling › should redirect route when requesting it directly

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 assetPrefix with basePath handling › should render link

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 assetPrefix with basePath handling › should redirect route when requesting it directly by browser

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 assetPrefix with basePath handling › should redirect route when clicking link

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 assetPrefix with basePath handling › bundles should return 200 on served assetPrefix

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 assetPrefix with basePath handling › rewrites › rewrites that do not start with assetPrefix should still work

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 assetPrefix with basePath handling › rewrites › should respect rewrites that start with assetPrefix

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.

__NEXT_EXPERIMENTAL_PPR=true pnpm test-start test/e2e/app-dir/app-a11y/index.test.ts (PPR)

  • app a11y features > route announcer > should not announce the initital title
  • app a11y features > route announcer > should announce document.title changes
  • app a11y features > route announcer > should announce h1 changes
  • app a11y features > route announcer > should announce route changes when h1 changes inside an inner layout
Expand output

● app a11y features › route announcer › should not announce the initital title

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 a11y features › route announcer › should announce document.title changes

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 a11y features › route announcer › should announce h1 changes

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 a11y features › route announcer › should announce route changes when h1 changes inside an inner layout

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.

__NEXT_EXPERIMENTAL_PPR=true pnpm test-start test/e2e/app-dir/app-basepath-custom-server/index.test.ts (PPR)

  • custom-app-server-action-redirect > redirects with basepath properly when server action handler uses redirect
  • custom-app-server-action-redirect > redirects with proper cookies set from both redirect response and post respose
Expand output

● custom-app-server-action-redirect › redirects with basepath properly when server action handler uses redirect

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)

● custom-app-server-action-redirect › redirects with proper cookies set from both redirect response and post respose

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.

__NEXT_EXPERIMENTAL_PPR=true pnpm test-start test/e2e/app-dir/catchall-parallel-routes-group/catchall-parallel-routes-group.test.ts (PPR)

  • catchall-parallel-routes-group > should work without throwing any errors about invalid pages
Expand output

● catchall-parallel-routes-group › should work without throwing any errors about invalid pages

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/app-dir/edge-errors-hmr/index.test.ts

  • develop - app-dir - edge errros hmr > should recover from build errors when server component error
  • develop - app-dir - edge errros hmr > should recover from build errors when client component error
Expand output

● develop - app-dir - edge errros hmr › should recover from build errors when server component error

Expected no visible Redbox but found one
header: Runtime TypeError
Server

Cannot set properties of undefined (setting 'resolvedMetadata')
description: Cannot set properties of undefined (setting 'resolvedMetadata')
source: null

  19 |     await next.patchFile('app/comp.server.js', clientComponentSource)
  20 |
> 21 |     await assertNoRedbox(browser)
     |     ^
  22 |   })
  23 |
  24 |   it('should recover from build errors when client component error', async () => {

  at Object.<anonymous> (development/app-dir/edge-errors-hmr/index.test.ts:21:5)

● develop - app-dir - edge errros hmr › should recover from build errors when client component error

Expected no visible Redbox but found one
header: Runtime TypeError
Server

Cannot set properties of undefined (setting 'resolvedMetadata')
description: Cannot set properties of undefined (setting 'resolvedMetadata')
source: null

  34 |     await next.patchFile('app/comp.client.js', clientComponentSource)
  35 |
> 36 |     await assertNoRedbox(browser)
     |     ^
  37 |   })
  38 | })
  39 |

  at Object.<anonymous> (development/app-dir/edge-errors-hmr/index.test.ts:36:5)

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

pnpm test test/integration/next-dynamic-css/test/index.test.js (turbopack)

  • next/dynamic > production mode > should load a Pages Router page correctly
  • next/dynamic > production mode > should load a App Router page correctly
Expand output

● next/dynamic › production mode › should load a Pages Router page correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 10.983217ms
 ✓ Compiled successfully in 3.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/4) ...
syncing resolvedMetadata from resolveMetadata undefined
   Generating static pages (1/4) 
Error occurred prerendering page "/test-app". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3776335692'
}
Export encountered an error on /test-app/page: /test-app, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● next/dynamic › production mode › should load a App Router page correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 10.983217ms
 ✓ Compiled successfully in 3.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/4) ...
syncing resolvedMetadata from resolveMetadata undefined
   Generating static pages (1/4) 
Error occurred prerendering page "/test-app". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3776335692'
}
Export encountered an error on /test-app/page: /test-app, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

  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/next-image-new/app-dir-localpatterns/test/index.test.ts (turbopack)

  • Image localPatterns config > production mode > should load matching images
  • Image localPatterns config > production mode > should block unmatched image does-not-exist
  • Image localPatterns config > production mode > should block unmatched image nested-assets-query
  • Image localPatterns config > production mode > should block unmatched image nested-blocked
  • Image localPatterns config > production mode > should block unmatched image top-level
  • Image localPatterns config > production mode > should build correct images-manifest.json
Expand output

● Image localPatterns config › production mode › should load matching images

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 11.988282ms
 ✓ Compiled successfully in 2.8s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/8) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/does-not-exist". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2566469324'
}
Export encountered an error on /does-not-exist/page: /does-not-exist, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should block unmatched image does-not-exist

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 11.988282ms
 ✓ Compiled successfully in 2.8s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/8) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/does-not-exist". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2566469324'
}
Export encountered an error on /does-not-exist/page: /does-not-exist, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should block unmatched image nested-assets-query

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 11.988282ms
 ✓ Compiled successfully in 2.8s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/8) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/does-not-exist". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2566469324'
}
Export encountered an error on /does-not-exist/page: /does-not-exist, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should block unmatched image nested-blocked

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 11.988282ms
 ✓ Compiled successfully in 2.8s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/8) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/does-not-exist". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2566469324'
}
Export encountered an error on /does-not-exist/page: /does-not-exist, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should block unmatched image top-level

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 11.988282ms
 ✓ Compiled successfully in 2.8s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/8) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/does-not-exist". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2566469324'
}
Export encountered an error on /does-not-exist/page: /does-not-exist, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should build correct images-manifest.json

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Turbopack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-localpatterns/next.config.js
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 11.988282ms
 ✓ Compiled successfully in 2.8s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/8) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/does-not-exist". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2566469324'
}
Export encountered an error on /does-not-exist/page: /does-not-exist, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

  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/next-dynamic-css-asset-prefix/test/index.test.js

  • next/dynamic with assetPrefix > production mode > should load a Pages Router page correctly
  • next/dynamic with assetPrefix > production mode > should load a App Router page correctly
Expand output

● next/dynamic with assetPrefix › production mode › should load a Pages Router page correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
 ✓ Compiled successfully in 6.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/4) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/test-app". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '728657808'
}
Export encountered an error on /test-app/page: /test-app, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● next/dynamic with assetPrefix › production mode › should load a App Router page correctly

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-dynamic-css-asset-prefix/next.config.js
 ✓ Compiled successfully in 6.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/4) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/test-app". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '728657808'
}
Export encountered an error on /test-app/page: /test-app, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

  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/next-image-new/app-dir-image-from-node-modules/test/index.test.ts

  • Image Component from node_modules prod mode > production mode > should apply image config for node_modules
Expand output

● Image Component from node_modules prod mode › production mode › should apply image config for node_modules

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-image-from-node-modules/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-image-from-node-modules/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-image-from-node-modules/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-image-from-node-modules/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-image-from-node-modules/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/4) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '2524556657'
}
Export encountered an error on /page: /, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

  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/next-image-new/app-dir-qualities/test/index.test.ts

  • Image localPatterns config > production mode > should load img when quality is undefined
  • Image localPatterns config > production mode > should load img when quality 42
  • Image localPatterns config > production mode > should load img when quality 69
  • Image localPatterns config > production mode > should load img when quality 88
  • Image localPatterns config > production mode > should fail to load img when quality is 100
  • Image localPatterns config > production mode > should build correct images-manifest.json
Expand output

● Image localPatterns config › production mode › should load img when quality is undefined

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/5) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/invalid-quality". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '988777193'
}
Export encountered an error on /invalid-quality/page: /invalid-quality, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should load img when quality 42

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/5) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/invalid-quality". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '988777193'
}
Export encountered an error on /invalid-quality/page: /invalid-quality, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should load img when quality 69

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/5) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/invalid-quality". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '988777193'
}
Export encountered an error on /invalid-quality/page: /invalid-quality, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should load img when quality 88

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/5) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/invalid-quality". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '988777193'
}
Export encountered an error on /invalid-quality/page: /invalid-quality, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should fail to load img when quality is 100

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/5) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/invalid-quality". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '988777193'
}
Export encountered an error on /invalid-quality/page: /invalid-quality, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Image localPatterns config › production mode › should build correct images-manifest.json

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   ▲ Next.js 15.4.0-canary.48 (Rspack)

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/next-image-new/app-dir-qualities/next.config.js
 ✓ Compiled successfully in 2000ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/5) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/invalid-quality". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '988777193'
}
Export encountered an error on /invalid-quality/page: /invalid-quality, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

  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/link-ref-app/test/index.test.js (turbopack)

  • Invalid hrefs > production mode > should not have a race condition with a click handler
  • Invalid hrefs > production mode > should preload with forwardRef
  • Invalid hrefs > production mode > should preload with child ref with React.createRef
  • Invalid hrefs > production mode > should preload with child ref with function
  • Invalid hrefs > production mode > should preload with child ref with function that returns a cleanup function
Expand output

● Invalid hrefs › production mode › should not have a race condition with a click handler

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

   Creating an optimized production build ...
   No config file found
   No config file found
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 8.168402ms
 ✓ Compiled successfully in 1966ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/10) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/child-ref". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3186025866'
}
Export encountered an error on /child-ref/page: /child-ref, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Invalid hrefs › production mode › should preload with forwardRef

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

   Creating an optimized production build ...
   No config file found
   No config file found
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 8.168402ms
 ✓ Compiled successfully in 1966ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/10) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/child-ref". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3186025866'
}
Export encountered an error on /child-ref/page: /child-ref, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Invalid hrefs › production mode › should preload with child ref with React.createRef

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

   Creating an optimized production build ...
   No config file found
   No config file found
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 8.168402ms
 ✓ Compiled successfully in 1966ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/10) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/child-ref". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3186025866'
}
Export encountered an error on /child-ref/page: /child-ref, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Invalid hrefs › production mode › should preload with child ref with function

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

   Creating an optimized production build ...
   No config file found
   No config file found
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 8.168402ms
 ✓ Compiled successfully in 1966ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/10) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/child-ref". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3186025866'
}
Export encountered an error on /child-ref/page: /child-ref, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● Invalid hrefs › production mode › should preload with child ref with function that returns a cleanup function

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

   Creating an optimized production build ...
   No config file found
   No config file found
 ✓ Starting to write all entrypoints to disk...
 ✓ Finished writing all entrypoints to disk in 8.168402ms
 ✓ Compiled successfully in 1966ms
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/10) ...
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/child-ref". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3186025866'
}
Export encountered an error on /child-ref/page: /child-ref, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

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

pnpm test-dev test/development/app-hmr/hmr.test.ts

  • app-dir-hmr > filesystem changes > should update server components after navigating to a page with a different runtime
  • app-dir-hmr > filesystem changes > should update server components pages when env files is changed (edge)
  • app-dir-hmr > filesystem changes > should update server components pages when env files is changed (edge-module-var)
Expand output

● app-dir-hmr › filesystem changes › should update server components after navigating to a page with a different runtime

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

Expected: "mac"
Received: "Cannot set properties of undefined (setting 'resolvedMetadata')"

  65 |       await browser.loadPage(`${next.url}/env/edge`)
  66 |       await browser.eval('window.__TEST_NO_RELOAD = true')
> 67 |       expect(await browser.elementByCss('p').text()).toBe('mac')
     |                                                      ^
  68 |
  69 |       const getCliOutput = next.getCliOutputFromHere()
  70 |       await next.patchFile(envFile, 'MY_DEVICE="ipad"', async () => {

  at Object.toBe (development/app-hmr/hmr.test.ts:67:54)

● app-dir-hmr › filesystem changes › should update server components pages when env files is changed (edge)

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

Expected: "mac"
Received: "Cannot set properties of undefined (setting 'resolvedMetadata')"

  112 |       async (page) => {
  113 |         const browser = await next.browser(`/env/${page}`)
> 114 |         expect(await browser.elementByCss('p').text()).toBe('mac')
      |                                                        ^
  115 |
  116 |         await next.patchFile(envFile, 'MY_DEVICE="ipad"', async () => {
  117 |           let logs

  at toBe (development/app-hmr/hmr.test.ts:114:56)

● app-dir-hmr › filesystem changes › should update server components pages when env files is changed (edge-module-var)

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

Expected: "mac"
Received: "Cannot set properties of undefined (setting 'resolvedMetadata')"

  112 |       async (page) => {
  113 |         const browser = await next.browser(`/env/${page}`)
> 114 |         expect(await browser.elementByCss('p').text()).toBe('mac')
      |                                                        ^
  115 |
  116 |         await next.patchFile(envFile, 'MY_DEVICE="ipad"', async () => {
  117 |           let logs

  at toBe (development/app-hmr/hmr.test.ts:114:56)

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

pnpm test-dev test/e2e/app-dir/app-edge/app-edge.test.ts

  • app-dir edge SSR > should resolve client component without error
Expand output

● app-dir edge SSR › should resolve client component without error

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

- Expected  - 1
+ Received  + 8

- Array []
+ Array [
+   " ⨯ Error [TypeError]: Cannot set properties of undefined (setting 'resolvedMetadata')
+     at JSON.parse (<anonymous>) {
+   environmentName: 'Server',
+   digest: '1884416627'
+ }
+ ",
+ ]

  79 |       const html = await next.render('/with-client')
  80 |       expect(html).toContain('My Button')
> 81 |       expect(logs).toEqual([])
     |                    ^
  82 |     })
  83 |
  84 |     it('should handle edge rsc hmr', async () => {

  at Object.toEqual (e2e/app-dir/app-edge/app-edge.test.ts:81:20)

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

pnpm test test/integration/root-catchall-cache/test/index.test.js

  • Root Catch-all Cache > production mode > should cache / correctly
Expand output

● Root Catch-all Cache › production mode › should cache / correctly

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

Expected: not ""

  42 |       await waitFor(100)
  43 |       const newRandom = await getRandom('/')
> 44 |       expect(random).not.toBe(newRandom)
     |                          ^
  45 |     }
  46 |   })
  47 | }

  at Object.toBe (integration/root-catchall-cache/test/index.test.js:44:26)

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

pnpm test test/integration/app-dir-export/test/dynamicpage-prod.test.ts

  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicPage undefined
  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicPage 'error'
  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicPage 'force-static'
  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicPage 'force-dynamic'
Expand output

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicPage undefined

thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

  14 |             'Page with `dynamic = "force-dynamic"` couldn\'t be exported. `output: "export"` requires all pages be renderable statically',
  15 |         },
> 16 |       ])(
     |        ^
  17 |         'should work in prod with dynamicPage $dynamicPage',
  18 |         async ({ dynamicPage, expectedErrMsg }) => {
  19 |           await runTests({ isDev: false, dynamicPage, expectedErrMsg })

  at ../node_modules/.pnpm/[email protected]/node_modules/jest-each/build/bind.js:47:15
      at Array.forEach (<anonymous>)
  at integration/app-dir-export/test/dynamicpage-prod.test.ts:16:8
  at integration/app-dir-export/test/dynamicpage-prod.test.ts:4:56
  at Object.describe (integration/app-dir-export/test/dynamicpage-prod.test.ts:3:1)

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicPage 'error'

Failed to replace content.

Pattern: export const dynamic = 'force-static'

Content: import Link from 'next/link'



export function generateStaticParams() {
  return [{ slug: 'first' }, { slug: 'second' }]
}

export default async function Page(props) {
  const params = await props.params
  return (
    <main>
      <h1>{params.slug}</h1>
      <ul>
        <li>
          <Link href="/another">Visit another page</Link>
        </li>
      </ul>
    </main>
  )
}

  769 |     } else if (typeof pattern === 'string') {
  770 |       if (!currentContent.includes(pattern)) {
> 771 |         throw new Error(
      |               ^
  772 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  773 |         )
  774 |       }

  at File.replace (lib/next-test-utils.ts:771:15)
  at replace (integration/app-dir-export/test/utils.ts:130:14)
  at integration/app-dir-export/test/dynamicpage-prod.test.ts:19:25

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicPage 'force-static'

Failed to replace content.

Pattern: export const dynamic = 'force-static'

Content: import Link from 'next/link'



export function generateStaticParams() {
  return [{ slug: 'first' }, { slug: 'second' }]
}

export default async function Page(props) {
  const params = await props.params
  return (
    <main>
      <h1>{params.slug}</h1>
      <ul>
        <li>
          <Link href="/another">Visit another page</Link>
        </li>
      </ul>
    </main>
  )
}

  769 |     } else if (typeof pattern === 'string') {
  770 |       if (!currentContent.includes(pattern)) {
> 771 |         throw new Error(
      |               ^
  772 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  773 |         )
  774 |       }

  at File.replace (lib/next-test-utils.ts:771:15)
  at replace (integration/app-dir-export/test/utils.ts:130:14)
  at integration/app-dir-export/test/dynamicpage-prod.test.ts:19:25

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicPage 'force-dynamic'

Failed to replace content.

Pattern: export const dynamic = 'force-static'

Content: import Link from 'next/link'



export function generateStaticParams() {
  return [{ slug: 'first' }, { slug: 'second' }]
}

export default async function Page(props) {
  const params = await props.params
  return (
    <main>
      <h1>{params.slug}</h1>
      <ul>
        <li>
          <Link href="/another">Visit another page</Link>
        </li>
      </ul>
    </main>
  )
}

  769 |     } else if (typeof pattern === 'string') {
  770 |       if (!currentContent.includes(pattern)) {
> 771 |         throw new Error(
      |               ^
  772 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  773 |         )
  774 |       }

  at File.replace (lib/next-test-utils.ts:771:15)
  at replace (integration/app-dir-export/test/utils.ts:130:14)
  at integration/app-dir-export/test/dynamicpage-prod.test.ts:19:25

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/e2e/app-dir/metadata-edge/index.test.ts (PPR)

  • app dir - Metadata API on the Edge runtime > should render OpenGraph image meta tag correctly
Expand output

● app dir - Metadata API on the Edge runtime › should render OpenGraph image meta tag correctly

TypeError: Invalid URL

  52 |   it('should render OpenGraph image meta tag correctly', async () => {
  53 |     const html$ = await next.render$('/')
> 54 |     const ogUrl = new URL(html$('meta[property="og:image"]').attr('content'))
     |                   ^
  55 |     const imageBuffer = await (await next.fetch(ogUrl.pathname)).buffer()
  56 |
  57 |     const size = imageSize(imageBuffer)

  at Object.<anonymous> (e2e/app-dir/metadata-edge/index.test.ts:54:19)

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

pnpm test test/integration/react-profiling-mode/test/index.test.js

  • React Profiling Mode > production mode > with config enabled > should have used the react-dom profiling bundle for pages
  • React Profiling Mode > production mode > with config enabled > should have used the react-dom profiling bundle for client component
  • React Profiling Mode > production mode > with config enabled > should have used the react-dom profiling bundle for server component
  • React Profiling Mode > production mode > without config enabled > should not have used the react-dom profiling bundle
Expand output

● React Profiling Mode › production mode › without config enabled › should not have used the react-dom profiling bundle

command failed with code 1 signal null
 ⚠ Linting is disabled.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
 ✓ Compiled successfully in 7.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/7) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/client". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3417097677'
}
Export encountered an error on /client/page: /client, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● React Profiling Mode › production mode › with config enabled › should have used the react-dom profiling bundle for pages

command failed with code 1 signal null
 ⚠ Linting is disabled.
 ⚠ Profiling is enabled. Note: This may affect performance.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
 ✓ Compiled successfully in 7.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/7) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/server". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3417097677'
}
Export encountered an error on /server/page: /server, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● React Profiling Mode › production mode › with config enabled › should have used the react-dom profiling bundle for client component

command failed with code 1 signal null
 ⚠ Linting is disabled.
 ⚠ Profiling is enabled. Note: This may affect performance.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
 ✓ Compiled successfully in 7.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/7) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/server". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3417097677'
}
Export encountered an error on /server/page: /server, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

● React Profiling Mode › production mode › with config enabled › should have used the react-dom profiling bundle for server component

command failed with code 1 signal null
 ⚠ Linting is disabled.
 ⚠ Profiling is enabled. Note: This may affect performance.
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   ▲ Next.js 15.4.0-canary.48

   Creating an optimized production build ...
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
   Loading config from /root/actions-runner/_work/next.js/next.js/test/integration/react-profiling-mode/next.config.js
 ✓ Compiled successfully in 7.0s
   Checking validity of types ...
   Collecting page data ...
   Generating static pages (0/7) ...
syncing resolvedMetadata from resolveMetadata undefined
Error occurred prerendering page "/server". Read more: https://nextjs.org/docs/messages/prerender-error
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
  digest: '3417097677'
}
Export encountered an error on /server/page: /server, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null

  312 |       ) {
  313 |         return reject(
> 314 |           new Error(
      |           ^
  315 |             `command failed with code ${code} signal ${signal}\n${mergedStdio}`
  316 |           )
  317 |         )

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

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/e2e/app-dir/dynamic/dynamic.test.ts (PPR)

  • app dir - next/dynamic > no SSR > should not render client component imported through ssr: false in client components in edge runtime
Expand output

● app dir - next/dynamic › no SSR › should not render client component imported through ssr: false in client components in edge runtime

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('#ssr-false-client-module')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Object.elementByCss (e2e/app-dir/dynamic/dynamic.test.ts:92:23)
  at Proxy._chain (lib/browsers/playwright.ts:568:23)
  at Proxy._chain (lib/browsers/playwright.ts:544:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:387:17)
  at Object.text (e2e/app-dir/dynamic/dynamic.test.ts:92:64)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/e2e/app-dir/next-image/next-image.test.ts (PPR)

  • app dir - next-image > browser content > should render images on / route
Expand output

● app dir - next-image › browser content › should render images on / route

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('#app-layout')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Playwright.elementByCss [as elementById] (lib/browsers/playwright.ts:379:17)
  at Object.elementById (e2e/app-dir/next-image/next-image.test.ts:161:36)

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

pnpm test-dev test/development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts

  • server-components-hmr-cache > edge runtime > should use cached fetch calls for fast refresh requests
  • server-components-hmr-cache > edge runtime > should not use cached fetch calls for intentional refresh requests
  • server-components-hmr-cache > edge runtime > in after() > should use cached fetch calls for fast refresh requests
  • server-components-hmr-cache > edge runtime > in after() > should not use cached fetch calls for intentional refresh requests
  • server-components-hmr-cache > edge runtime > with experimental.serverComponentsHmrCache disabled > should not use cached fetch calls for fast refresh requests
Expand output

● server-components-hmr-cache › edge runtime › should use cached fetch calls for fast refresh requests

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('#value')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Playwright.elementByCss [as elementById] (lib/browsers/playwright.ts:379:17)
  at Object.elementById (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:23:46)
  at Proxy._chain (lib/browsers/playwright.ts:568:23)
  at Proxy._chain (lib/browsers/playwright.ts:544:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:387:17)
  at Object.text (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:23:67)

● server-components-hmr-cache › edge runtime › should not use cached fetch calls for intentional refresh requests

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('#value')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Playwright.elementByCss [as elementById] (lib/browsers/playwright.ts:379:17)
  at Object.elementById (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:43:48)
  at Proxy._chain (lib/browsers/playwright.ts:568:23)
  at Proxy._chain (lib/browsers/playwright.ts:544:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:387:17)
  at Object.text (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:43:69)

● server-components-hmr-cache › edge runtime › in after() › should use cached fetch calls for fast refresh requests

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

Expected: "0.6302096001995532"
Received: "0.5456542981951094"

  72 |
  73 |             const valueAfterPatch = getLoggedAfterValue()
> 74 |             expect(valueBeforePatch).toEqual(valueAfterPatch)
     |                                      ^
  75 |           }
  76 |         )
  77 |       })

  at toEqual (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:74:38)
  at NextDevInstance.patchFile (lib/next-modes/base.ts:601:9)
  at NextDevInstance.patchFile (lib/next-modes/next-dev.ts:199:16)
  at Object.<anonymous> (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:63:9)

● server-components-hmr-cache › edge runtime › in after() › should not use cached fetch calls for intentional refresh requests

No logs from after() found

  13 |
  14 |     if (!match) {
> 15 |       throw new Error('No logs from after() found')
     |             ^
  16 |     }
  17 |     return match[1]
  18 |   }

  at getLoggedAfterValue (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:15:13)
  at getLoggedAfterValue (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:87:37)
  at fn (lib/next-test-utils.ts:811:20)
  at Object.<anonymous> (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:86:9)

● server-components-hmr-cache › edge runtime › with experimental.serverComponentsHmrCache disabled › should not use cached fetch calls for fast refresh requests

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('#value')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Playwright.elementByCss [as elementById] (lib/browsers/playwright.ts:379:17)
  at Object.elementById (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:115:48)
  at Proxy._chain (lib/browsers/playwright.ts:568:23)
  at Proxy._chain (lib/browsers/playwright.ts:544:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:387:17)
  at Object.text (development/app-dir/server-components-hmr-cache/server-components-hmr-cache.test.ts:115:69)

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

pnpm test-dev test/e2e/app-dir/next-image/next-image-proxy.test.ts

  • next-image-proxy > loads images without any errors
Expand output

● next-image-proxy › loads images without any errors

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('#app-page')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Object.elementByCss (e2e/app-dir/next-image/next-image-proxy.test.ts:79:33)
  at Proxy._chain (lib/browsers/playwright.ts:568:23)
  at Proxy._chain (lib/browsers/playwright.ts:544:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:409:17)
  at Object.getAttribute (e2e/app-dir/next-image/next-image-proxy.test.ts:79:59)

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

pnpm test-dev test/e2e/app-dir/dynamic-css/index.test.ts

  • app dir - dynamic css > should only apply corresponding css for page loaded in edge runtime
Expand output

● app dir - dynamic css › should only apply corresponding css for page loaded in edge runtime

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

Expected: "rgb(255, 0, 0)"
Received: null

  46 |           `window.getComputedStyle(document.querySelector('.text')).color`
  47 |         )
> 48 |       ).toBe('rgb(255, 0, 0)')
     |         ^
  49 |       // Default border width, which is not effected by bar.css that is not loaded in /ssr
  50 |       expect(
  51 |         await browser.eval(

  at toBe (e2e/app-dir/dynamic-css/index.test.ts:48:9)
  at retry (lib/next-test-utils.ts:811:14)
  at Object.<anonymous> (e2e/app-dir/dynamic-css/index.test.ts:43:5)

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

pnpm test-dev-turbo test/e2e/app-dir/interception-route-prefetch-cache/interception-route-prefetch-cache.test.ts (turbopack)

  • interception-route-prefetch-cache > runtime = edge > should render the correct interception when two distinct layouts share the same path structure
Expand output

● interception-route-prefetch-cache › runtime = edge › should render the correct interception when two distinct layouts share the same path structure

page.waitForSelector: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('[href="/foo"]')

  454 |   waitForElementByCss(selector: string, timeout = 10_000) {
  455 |     return this.startChain(async () => {
> 456 |       const el = await page.waitForSelector(selector, {
      |                             ^
  457 |         timeout,
  458 |         state: 'attached',
  459 |       })

  at waitForSelector (lib/browsers/playwright.ts:456:29)
  at Playwright._chain (lib/browsers/playwright.ts:568:23)
  at Playwright._chain [as startChain] (lib/browsers/playwright.ts:549:17)
  at Playwright.startChain [as waitForElementByCss] (lib/browsers/playwright.ts:455:17)
  at Playwright.waitForElementByCss [as elementByCss] (lib/browsers/playwright.ts:375:17)
  at Object.elementByCss (e2e/app-dir/interception-route-prefetch-cache/interception-route-prefetch-cache.test.ts:11:21)
  at Proxy._chain (lib/browsers/playwright.ts:568:23)
  at Proxy._chain (lib/browsers/playwright.ts:544:17)
  at Proxy.continueChain (lib/browsers/playwright.ts:425:17)
  at Object.click (e2e/app-dir/interception-route-prefetch-cache/interception-route-prefetch-cache.test.ts:11:51)

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

pnpm test test/integration/app-dir-export/test/dynamicapiroute-prod.test.ts

  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicApiRoute 'error'
  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicApiRoute 'force-static'
  • app dir - with output export - dynamic api route prod > production mode > should work in prod with dynamicApiRoute 'force-dynamic'
Expand output

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicApiRoute 'error'

thrown: "Exceeded timeout of 60000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."

  18 |             'export const dynamic = "force-dynamic" on page "/api/json" cannot be used with "output: export".',
  19 |         },
> 20 |       ])(
     |        ^
  21 |         'should work in prod with dynamicApiRoute $dynamicApiRoute',
  22 |         async ({ dynamicApiRoute, expectedErrMsg }) => {
  23 |           await runTests({ isDev: false, dynamicApiRoute, expectedErrMsg })

  at ../node_modules/.pnpm/[email protected]/node_modules/jest-each/build/bind.js:47:15
      at Array.forEach (<anonymous>)
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:20:8
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:4:56
  at Object.describe (integration/app-dir-export/test/dynamicapiroute-prod.test.ts:3:1)

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicApiRoute 'force-static'

Failed to replace content.

Pattern: export const dynamic = 'force-static'

Content: export const dynamic = 'error'

export async function GET() {
  return Response.json({ answer: 42 })
}

  769 |     } else if (typeof pattern === 'string') {
  770 |       if (!currentContent.includes(pattern)) {
> 771 |         throw new Error(
      |               ^
  772 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  773 |         )
  774 |       }

  at File.replace (lib/next-test-utils.ts:771:15)
  at replace (integration/app-dir-export/test/utils.ts:137:13)
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:23:25

● app dir - with output export - dynamic api route prod › production mode › should work in prod with dynamicApiRoute 'force-dynamic'

Failed to replace content.

Pattern: export const dynamic = 'force-static'

Content: export const dynamic = 'error'

export async function GET() {
  return Response.json({ answer: 42 })
}

  769 |     } else if (typeof pattern === 'string') {
  770 |       if (!currentContent.includes(pattern)) {
> 771 |         throw new Error(
      |               ^
  772 |           `Failed to replace content.\n\nPattern: ${pattern}\n\nContent: ${currentContent}`
  773 |         )
  774 |       }

  at File.replace (lib/next-test-utils.ts:771:15)
  at replace (integration/app-dir-export/test/utils.ts:137:13)
  at integration/app-dir-export/test/dynamicapiroute-prod.test.ts:23:25

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

pnpm test-dev-turbo test/development/app-dir/ssr-in-rsc/ssr-in-rsc.test.ts (turbopack)

  • react-dom/server in React Server environment > implicit react-dom/server.edge usage in library code
Expand output

● react-dom/server in React Server environment › implicit react-dom/server.edge usage in library code

Expected no visible Redbox but found one
header: Runtime TypeError
Server

Cannot set properties of undefined (setting 'resolvedMetadata')
description: Cannot set properties of undefined (setting 'resolvedMetadata')
source: null

  667 |     )
  668 |
> 669 |     await assertNoRedbox(browser)
      |     ^
  670 |     if (isTurbopack) {
  671 |       if (isReactExperimental) {
  672 |         expect(await browser.elementByCss('main').text())

  at Object.<anonymous> (development/app-dir/ssr-in-rsc/ssr-in-rsc.test.ts:669:5)

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

@ijjk
Copy link
Member

ijjk commented May 23, 2025

Stats from current PR

Default Build (Increase detected ⚠️)
General Overall increase ⚠️
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
buildDuration 20.9s 17.6s N/A
buildDurationCached 16.8s 14.5s N/A
nodeModulesSize 428 MB 428 MB ⚠️ +134 kB
nextStartRea..uration (ms) 463ms 466ms N/A
Client Bundles (main, webpack) Overall increase ⚠️
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
1733-HASH.js gzip 44.5 kB 45 kB ⚠️ +470 B
194b18f3-HASH.js gzip 53.8 kB 53.8 kB N/A
2192.HASH.js gzip 169 B 169 B
4719-HASH.js gzip 5.47 kB 5.44 kB N/A
framework-HASH.js gzip 57.4 kB 57.4 kB
main-app-HASH.js gzip 254 B 256 B N/A
main-HASH.js gzip 33.5 kB 33.6 kB N/A
webpack-HASH.js gzip 1.71 kB 1.71 kB N/A
Overall change 102 kB 103 kB ⚠️ +470 B
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object 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 jiwon/05-23-_dev-tools_display_metadata_object Change
_app-HASH.js gzip 193 B 193 B
_error-HASH.js gzip 192 B 192 B
amp-HASH.js gzip 510 B 510 B
css-HASH.js gzip 344 B 342 B N/A
dynamic-HASH.js gzip 1.84 kB 1.83 kB N/A
edge-ssr-HASH.js gzip 265 B 265 B
head-HASH.js gzip 363 B 364 B N/A
hooks-HASH.js gzip 392 B 391 B N/A
image-HASH.js gzip 4.69 kB 4.67 kB N/A
index-HASH.js gzip 267 B 267 B
link-HASH.js gzip 2.53 kB 2.53 kB N/A
routerDirect..HASH.js gzip 328 B 325 B N/A
script-HASH.js gzip 396 B 396 B
withRouter-HASH.js gzip 325 B 325 B
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 2.25 kB 2.25 kB
Client Build Manifests
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
_buildManifest.js gzip 751 B 749 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
index.html gzip 530 B 530 B
link.html gzip 541 B 542 B N/A
withRouter.html gzip 526 B 524 B N/A
Overall change 530 B 530 B
Edge SSR bundle Size
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
edge-ssr.js gzip 141 kB 140 kB N/A
page.js gzip 220 kB 214 kB N/A
Overall change 0 B 0 B
Middleware size Overall increase ⚠️
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
middleware-b..fest.js gzip 677 B 677 B
middleware-r..fest.js gzip 155 B 157 B N/A
middleware.js gzip 32.5 kB 32.7 kB ⚠️ +172 B
edge-runtime..pack.js gzip 853 B 853 B
Overall change 34 kB 34.2 kB ⚠️ +172 B
Next Runtimes Overall increase ⚠️
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
app-page-exp...dev.js gzip 322 kB 322 kB ⚠️ +362 B
app-page-exp..prod.js gzip 150 kB 150 kB
app-page-tur...dev.js gzip 322 kB 322 kB ⚠️ +350 B
app-page-tur..prod.js gzip 150 kB 150 kB
app-page-tur...dev.js gzip 313 kB 314 kB ⚠️ +348 B
app-page-tur..prod.js gzip 146 kB 146 kB
app-page.run...dev.js gzip 313 kB 313 kB ⚠️ +350 B
app-page.run..prod.js gzip 146 kB 146 kB
app-route-ex...dev.js gzip 60.5 kB 60.5 kB
app-route-ex..prod.js gzip 39.5 kB 39.5 kB
app-route-tu...dev.js gzip 60.6 kB 60.6 kB
app-route-tu..prod.js gzip 39.5 kB 39.5 kB
app-route-tu...dev.js gzip 60 kB 60 kB
app-route-tu..prod.js gzip 39.1 kB 39.1 kB
app-route.ru...dev.js gzip 59.9 kB 59.9 kB
app-route.ru..prod.js gzip 39.1 kB 39.1 kB
dist_client_...dev.js gzip 326 B 326 B
dist_client_...dev.js gzip 328 B 328 B
dist_client_...dev.js gzip 320 B 320 B
dist_client_...dev.js gzip 318 B 318 B
pages-api-tu...dev.js gzip 30 kB 30 kB
pages-api-tu..prod.js gzip 21.4 kB 21.4 kB
pages-api.ru...dev.js gzip 30 kB 30 kB
pages-api.ru..prod.js gzip 21.4 kB 21.4 kB
pages-turbo....dev.js gzip 43.7 kB 43.7 kB
pages-turbo...prod.js gzip 32 kB 32 kB
pages.runtim...dev.js gzip 43.9 kB 43.9 kB
pages.runtim..prod.js gzip 32.1 kB 32.1 kB
server.runti..prod.js gzip 67 kB 67.1 kB N/A
Overall change 2.52 MB 2.52 MB ⚠️ +1.41 kB
build cache Overall increase ⚠️
vercel/next.js canary vercel/next.js jiwon/05-23-_dev-tools_display_metadata_object Change
0.pack gzip 2.48 MB 2.49 MB ⚠️ +3.98 kB
index.pack gzip 78.1 kB 79.4 kB ⚠️ +1.22 kB
Overall change 2.56 MB 2.57 MB ⚠️ +5.21 kB
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 css-HASH.js
@@ -1,7 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [9813],
   {
-    /***/ 1586: /***/ (
+    /***/ 2628: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -9,7 +9,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/css",
         function () {
-          return __webpack_require__(4362);
+          return __webpack_require__(8707);
         },
       ]);
       if (false) {
@@ -18,14 +18,7 @@
       /***/
     },
 
-    /***/ 4350: /***/ (module) => {
-      // extracted by mini-css-extract-plugin
-      module.exports = { helloWorld: "css_helloWorld__aUdUq" };
-
-      /***/
-    },
-
-    /***/ 4362: /***/ (
+    /***/ 8707: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -39,7 +32,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(5640);
       /* harmony import */ var _css_module_css__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(4350);
+        __webpack_require__(9080);
       /* harmony import */ var _css_module_css__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           _css_module_css__WEBPACK_IMPORTED_MODULE_1__
@@ -58,13 +51,20 @@
 
       /***/
     },
+
+    /***/ 9080: /***/ (module) => {
+      // extracted by mini-css-extract-plugin
+      module.exports = { helloWorld: "css_helloWorld__aUdUq" };
+
+      /***/
+    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(1586)
+      __webpack_exec__(2628)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for dynamic-HASH.js
@@ -1,17 +1,63 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [2291],
   {
-    /***/ 283: /***/ (
-      module,
-      __unused_webpack_exports,
+    /***/ 2001: /***/ (
+      __unused_webpack_module,
+      __webpack_exports__,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(6990);
+      "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__(5640);
+      /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1__ =
+        __webpack_require__(9553);
+      /* 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() */ 8042)
+            .then(__webpack_require__.bind(__webpack_require__, 8042))
+            .then((mod) => mod.Hello),
+        {
+          loadableGenerated: {
+            webpack: () => [/*require.resolve*/ 8042],
+          },
+        }
+      );
+      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;
 
       /***/
     },
 
-    /***/ 505: /***/ (
+    /***/ 2210: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -53,7 +99,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       const _react = /*#__PURE__*/ _interop_require_default._(
         __webpack_require__(148)
       );
-      const _loadablecontextsharedruntime = __webpack_require__(6179);
+      const _loadablecontextsharedruntime = __webpack_require__(7807);
       function resolve(obj) {
         return obj && obj.default ? obj.default : obj;
       }
@@ -288,63 +334,24 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       /***/
     },
 
-    /***/ 5703: /***/ (
+    /***/ 2976: /***/ (
       __unused_webpack_module,
-      __webpack_exports__,
+      __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__(5640);
-      /* harmony import */ var next_dynamic__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(283);
-      /* 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() */ 2192)
-            .then(__webpack_require__.bind(__webpack_require__, 2192))
-            .then((mod) => mod.Hello),
-        {
-          loadableGenerated: {
-            webpack: () => [/*require.resolve*/ 2192],
-          },
-        }
-      );
-      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;
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/dynamic",
+        function () {
+          return __webpack_require__(2001);
+        },
+      ]);
+      if (false) {
+      }
 
       /***/
     },
 
-    /***/ 6179: /***/ (
+    /***/ 7807: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -371,7 +378,17 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
       /***/
     },
 
-    /***/ 6990: /***/ (module, exports, __webpack_require__) => {
+    /***/ 9553: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(9986);
+
+      /***/
+    },
+
+    /***/ 9986: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -404,7 +421,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
         __webpack_require__(148)
       );
       const _loadablesharedruntime = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(505)
+        __webpack_require__(2210)
       );
       const isServerSide = "object" === "undefined";
       // Normalize loader to return the module as form { default: Component } for `React.lazy`.
@@ -504,30 +521,13 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE
 
       /***/
     },
-
-    /***/ 9254: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/dynamic",
-        function () {
-          return __webpack_require__(5703);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(9254)
+      __webpack_exec__(2976)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for hooks-HASH.js
@@ -1,24 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [9804],
   {
-    /***/ 1664: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/hooks",
-        function () {
-          return __webpack_require__(6130);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
-
-    /***/ 6130: /***/ (
+    /***/ 4756: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -76,13 +59,30 @@
 
       /***/
     },
+
+    /***/ 5426: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/hooks",
+        function () {
+          return __webpack_require__(4756);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(1664)
+      __webpack_exec__(5426)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for image-HASH.js
@@ -1,7 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [2983],
   {
-    /***/ 2198: /***/ (
+    /***/ 264: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -9,7 +9,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/image",
         function () {
-          return __webpack_require__(3444);
+          return __webpack_require__(3594);
         },
       ]);
       if (false) {
@@ -18,7 +18,190 @@
       /***/
     },
 
-    /***/ 2514: /***/ (
+    /***/ 1206: /***/ (__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
+
+      /***/
+    },
+
+    /***/ 1765: /***/ (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__(148);
+      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
+
+      /***/
+    },
+
+    /***/ 3353: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(5526);
+
+      /***/
+    },
+
+    /***/ 3594: /***/ (
+      __unused_webpack_module,
+      __webpack_exports__,
+      __webpack_require__
+    ) => {
+      "use strict";
+      // ESM COMPAT FLAG
+      __webpack_require__.r(__webpack_exports__);
+
+      // EXPORTS
+      __webpack_require__.d(__webpack_exports__, {
+        __N_SSP: () => /* binding */ __N_SSP,
+        default: () => /* binding */ pages_image,
+      });
+
+      // EXTERNAL MODULE: ./node_modules/.pnpm/[email protected]/node_modules/react/jsx-runtime.js
+      var jsx_runtime = __webpack_require__(5640);
+      // EXTERNAL MODULE: ./node_modules/.pnpm/next@[email protected][email protected][email protected]/node_modules/next/image.js
+      var next_image = __webpack_require__(3353);
+      var image_default = /*#__PURE__*/ __webpack_require__.n(next_image); // ./pages/nextjs.png
+      /* harmony default export */ const nextjs = {
+        src: "/_next/static/media/nextjs.cae0b805.png",
+        height: 1347,
+        width: 1626,
+        blurDataURL:
+          "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAAHCAMAAAACh/xsAAAAD1BMVEX////x8fH6+vrb29vo6Oh8o70bAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAH0lEQVR4nGNgwARMjIyMjCAGCzMzMwsTRISJCcRABwAEcAAkLCQfgAAAAABJRU5ErkJggg==",
+        blurWidth: 8,
+        blurHeight: 7,
+      }; // ./pages/image.js
+      function ImagePage(props) {
+        return /*#__PURE__*/ (0, jsx_runtime.jsxs)(jsx_runtime.Fragment, {
+          children: [
+            /*#__PURE__*/ (0, jsx_runtime.jsx)("h1", {
+              children: "next/image example",
+            }),
+            /*#__PURE__*/ (0, jsx_runtime.jsx)(image_default(), {
+              src: nextjs,
+              placeholder: "blur",
+            }),
+          ],
+        });
+      }
+      var __N_SSP = true;
+      /* harmony default export */ const pages_image = ImagePage;
+
+      /***/
+    },
+
+    /***/ 3854: /***/ (
       __unused_webpack_module,
       exports,
       __webpack_require__
@@ -34,9 +217,9 @@
           return getImgProps;
         },
       });
-      const _warnonce = __webpack_require__(5127);
-      const _imageblursvg = __webpack_require__(4287);
-      const _imageconfig = __webpack_require__(2795);
+      const _warnonce = __webpack_require__(3603);
+      const _imageblursvg = __webpack_require__(7835);
+      const _imageconfig = __webpack_require__(6799);
       const VALID_LOADING_VALUES =
         /* unused pure expression or super */ null && [
           "lazy",
@@ -463,55 +646,69 @@
       /***/
     },
 
-    /***/ 3444: /***/ (
+    /***/ 5526: /***/ (
       __unused_webpack_module,
-      __webpack_exports__,
+      exports,
       __webpack_require__
     ) => {
       "use strict";
-      // ESM COMPAT FLAG
-      __webpack_require__.r(__webpack_exports__);
 
-      // EXPORTS
-      __webpack_require__.d(__webpack_exports__, {
-        __N_SSP: () => /* binding */ __N_SSP,
-        default: () => /* binding */ pages_image,
+      Object.defineProperty(exports, "__esModule", {
+        value: true,
       });
-
-      // EXTERNAL MODULE: ./node_modules/.pnpm/[email protected]/node_modules/react/jsx-runtime.js
-      var jsx_runtime = __webpack_require__(5640);
-      // EXTERNAL MODULE: ./node_modules/.pnpm/next@[email protected][email protected][email protected]/node_modules/next/image.js
-      var next_image = __webpack_require__(6359);
-      var image_default = /*#__PURE__*/ __webpack_require__.n(next_image); // ./pages/nextjs.png
-      /* harmony default export */ const nextjs = {
-        src: "/_next/static/media/nextjs.cae0b805.png",
-        height: 1347,
-        width: 1626,
-        blurDataURL:
-          "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAAHCAMAAAACh/xsAAAAD1BMVEX////x8fH6+vrb29vo6Oh8o70bAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAH0lEQVR4nGNgwARMjIyMjCAGCzMzMwsTRISJCcRABwAEcAAkLCQfgAAAAABJRU5ErkJggg==",
-        blurWidth: 8,
-        blurHeight: 7,
-      }; // ./pages/image.js
-      function ImagePage(props) {
-        return /*#__PURE__*/ (0, jsx_runtime.jsxs)(jsx_runtime.Fragment, {
-          children: [
-            /*#__PURE__*/ (0, jsx_runtime.jsx)("h1", {
-              children: "next/image example",
-            }),
-            /*#__PURE__*/ (0, jsx_runtime.jsx)(image_default(), {
-              src: nextjs,
-              placeholder: "blur",
-            }),
-          ],
+      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__(3854);
+      const _imagecomponent = __webpack_require__(8350);
+      const _imageloader = /*#__PURE__*/ _interop_require_default._(
+        __webpack_require__(1206)
+      );
+      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,
+        };
       }
-      var __N_SSP = true;
-      /* harmony default export */ const pages_image = ImagePage;
+      const _default = _imagecomponent.Image; //# sourceMappingURL=image-external.js.map
 
       /***/
     },
 
-    /***/ 4287: /***/ (__unused_webpack_module, exports) => {
+    /***/ 7835: /***/ (__unused_webpack_module, exports) => {
       "use strict";
       /**
        * A shared function, used on both client and server, to generate a SVG blur placeholder.
@@ -566,85 +763,7 @@
       /***/
     },
 
-    /***/ 4985: /***/ (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__(148);
-      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
-
-      /***/
-    },
-
-    /***/ 5898: /***/ (module, exports, __webpack_require__) => {
+    /***/ 8350: /***/ (module, exports, __webpack_require__) => {
       "use strict";
       /* __next_internal_client_entry_do_not_use__  cjs */
       Object.defineProperty(exports, "__esModule", {
@@ -666,17 +785,17 @@
         __webpack_require__(7897)
       );
       const _head = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(5207)
+        __webpack_require__(8843)
       );
-      const _getimgprops = __webpack_require__(2514);
-      const _imageconfig = __webpack_require__(2795);
-      const _imageconfigcontextsharedruntime = __webpack_require__(2349);
-      const _warnonce = __webpack_require__(5127);
-      const _routercontextsharedruntime = __webpack_require__(3556);
+      const _getimgprops = __webpack_require__(3854);
+      const _imageconfig = __webpack_require__(6799);
+      const _imageconfigcontextsharedruntime = __webpack_require__(3905);
+      const _warnonce = __webpack_require__(3603);
+      const _routercontextsharedruntime = __webpack_require__(6712);
       const _imageloader = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(5970)
+        __webpack_require__(1206)
       );
-      const _usemergedref = __webpack_require__(4985);
+      const _usemergedref = __webpack_require__(1765);
       // This is replaced by webpack define plugin
       const configEnv = {
         deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
@@ -1002,132 +1121,13 @@
 
       /***/
     },
-
-    /***/ 5970: /***/ (__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
-
-      /***/
-    },
-
-    /***/ 6359: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(8986);
-
-      /***/
-    },
-
-    /***/ 8986: /***/ (
-      __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__(2514);
-      const _imagecomponent = __webpack_require__(5898);
-      const _imageloader = /*#__PURE__*/ _interop_require_default._(
-        __webpack_require__(5970)
-      );
-      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
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(2198)
+      __webpack_exec__(264)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for index-HASH.js
@@ -1,7 +1,24 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [3332],
   {
-    /***/ 9418: /***/ (
+    /***/ 8230: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/",
+        function () {
+          return __webpack_require__(8696);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 8696: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -19,30 +36,13 @@
 
       /***/
     },
-
-    /***/ 9532: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/",
-        function () {
-          return __webpack_require__(9418);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(9532)
+      __webpack_exec__(8230)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for link-HASH.js
@@ -1,125 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [4672],
   {
-    /***/ 1854: /***/ (
-      __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__(5640);
-      /* harmony import */ var next_link__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(8770);
-      /* 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;
-
-      /***/
-    },
-
-    /***/ 3199: /***/ (__unused_webpack_module, exports) => {
-      "use strict";
-
-      Object.defineProperty(exports, "__esModule", {
-        value: true,
-      });
-      Object.defineProperty(exports, "errorOnce", {
-        enumerable: true,
-        get: function () {
-          return errorOnce;
-        },
-      });
-      let errorOnce = (_) => {};
-      if (false) {
-      } //# sourceMappingURL=error-once.js.map
-
-      /***/
-    },
-
-    /***/ 3568: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/link",
-        function () {
-          return __webpack_require__(1854);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
-
-    /***/ 3857: /***/ (module, exports, __webpack_require__) => {
-      "use strict";
-
-      Object.defineProperty(exports, "__esModule", {
-        value: true,
-      });
-      Object.defineProperty(exports, "getDomainLocale", {
-        enumerable: true,
-        get: function () {
-          return getDomainLocale;
-        },
-      });
-      const _normalizetrailingslash = __webpack_require__(4869);
-      const basePath =
-        /* unused pure expression or super */ null && (false || "");
-      function getDomainLocale(path, locale, locales, domainLocales) {
-        if (false) {
-        } else {
-          return false;
-        }
-      }
-      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=get-domain-locale.js.map
-
-      /***/
-    },
-
-    /***/ 3947: /***/ (module, exports, __webpack_require__) => {
+    /***/ 591: /***/ (module, exports, __webpack_require__) => {
       "use strict";
       /* __next_internal_client_entry_do_not_use__  cjs */
       Object.defineProperty(exports, "__esModule", {
@@ -146,17 +28,17 @@
       const _react = /*#__PURE__*/ _interop_require_wildcard._(
         __webpack_require__(148)
       );
-      const _resolvehref = __webpack_require__(3161);
-      const _islocalurl = __webpack_require__(2309);
-      const _formaturl = __webpack_require__(3768);
-      const _utils = __webpack_require__(5554);
-      const _addlocale = __webpack_require__(7591);
-      const _routercontextsharedruntime = __webpack_require__(3556);
-      const _useintersection = __webpack_require__(5624);
-      const _getdomainlocale = __webpack_require__(3857);
-      const _addbasepath = __webpack_require__(4356);
-      const _usemergedref = __webpack_require__(4985);
-      const _erroronce = __webpack_require__(3199);
+      const _resolvehref = __webpack_require__(5837);
+      const _islocalurl = __webpack_require__(5953);
+      const _formaturl = __webpack_require__(6212);
+      const _utils = __webpack_require__(6950);
+      const _addlocale = __webpack_require__(6467);
+      const _routercontextsharedruntime = __webpack_require__(6712);
+      const _useintersection = __webpack_require__(9692);
+      const _getdomainlocale = __webpack_require__(6850);
+      const _addbasepath = __webpack_require__(4928);
+      const _usemergedref = __webpack_require__(1765);
+      const _erroronce = __webpack_require__(8659);
       const prefetched = new Set();
       function prefetch(router, href, as, options) {
         if (false) {
@@ -545,7 +427,17 @@
       /***/
     },
 
-    /***/ 4985: /***/ (module, exports, __webpack_require__) => {
+    /***/ 1148: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(591);
+
+      /***/
+    },
+
+    /***/ 1765: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -623,7 +515,125 @@
       /***/
     },
 
-    /***/ 5624: /***/ (module, exports, __webpack_require__) => {
+    /***/ 5436: /***/ (
+      __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__(5640);
+      /* harmony import */ var next_link__WEBPACK_IMPORTED_MODULE_1__ =
+        __webpack_require__(1148);
+      /* 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;
+
+      /***/
+    },
+
+    /***/ 6850: /***/ (module, exports, __webpack_require__) => {
+      "use strict";
+
+      Object.defineProperty(exports, "__esModule", {
+        value: true,
+      });
+      Object.defineProperty(exports, "getDomainLocale", {
+        enumerable: true,
+        get: function () {
+          return getDomainLocale;
+        },
+      });
+      const _normalizetrailingslash = __webpack_require__(6457);
+      const basePath =
+        /* unused pure expression or super */ null && (false || "");
+      function getDomainLocale(path, locale, locales, domainLocales) {
+        if (false) {
+        } else {
+          return false;
+        }
+      }
+      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=get-domain-locale.js.map
+
+      /***/
+    },
+
+    /***/ 8659: /***/ (__unused_webpack_module, exports) => {
+      "use strict";
+
+      Object.defineProperty(exports, "__esModule", {
+        value: true,
+      });
+      Object.defineProperty(exports, "errorOnce", {
+        enumerable: true,
+        get: function () {
+          return errorOnce;
+        },
+      });
+      let errorOnce = (_) => {};
+      if (false) {
+      } //# sourceMappingURL=error-once.js.map
+
+      /***/
+    },
+
+    /***/ 9666: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/link",
+        function () {
+          return __webpack_require__(5436);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 9692: /***/ (module, exports, __webpack_require__) => {
       "use strict";
 
       Object.defineProperty(exports, "__esModule", {
@@ -636,7 +646,7 @@
         },
       });
       const _react = __webpack_require__(148);
-      const _requestidlecallback = __webpack_require__(3543);
+      const _requestidlecallback = __webpack_require__(315);
       const hasIntersectionObserver =
         typeof IntersectionObserver === "function";
       const observers = new Map();
@@ -748,23 +758,13 @@
 
       /***/
     },
-
-    /***/ 8770: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(3947);
-
-      /***/
-    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(3568)
+      __webpack_exec__(9666)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for routerDirect-HASH.js
@@ -1,7 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [188],
   {
-    /***/ 3618: /***/ (
+    /***/ 76: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -16,7 +16,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(5640);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(4631);
+        __webpack_require__(9413);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_router__WEBPACK_IMPORTED_MODULE_1__
@@ -36,17 +36,7 @@
       /***/
     },
 
-    /***/ 4631: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(7086);
-
-      /***/
-    },
-
-    /***/ 7824: /***/ (
+    /***/ 1810: /***/ (
       __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
@@ -54,7 +44,7 @@
       (window.__NEXT_P = window.__NEXT_P || []).push([
         "/routerDirect",
         function () {
-          return __webpack_require__(3618);
+          return __webpack_require__(76);
         },
       ]);
       if (false) {
@@ -62,13 +52,23 @@
 
       /***/
     },
+
+    /***/ 9413: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(5282);
+
+      /***/
+    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(7824)
+      __webpack_exec__(1810)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for script-HASH.js
@@ -1,24 +1,17 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [1209],
   {
-    /***/ 1984: /***/ (
-      __unused_webpack_module,
+    /***/ 2227: /***/ (
+      module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/script",
-        function () {
-          return __webpack_require__(5769);
-        },
-      ]);
-      if (false) {
-      }
+      module.exports = __webpack_require__(5984);
 
       /***/
     },
 
-    /***/ 5769: /***/ (
+    /***/ 3043: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -33,7 +26,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(5640);
       /* harmony import */ var next_script__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(8293);
+        __webpack_require__(2227);
       /* harmony import */ var next_script__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_script__WEBPACK_IMPORTED_MODULE_1__
@@ -66,12 +59,19 @@
       /***/
     },
 
-    /***/ 8293: /***/ (
-      module,
+    /***/ 3642: /***/ (
+      __unused_webpack_module,
       __unused_webpack_exports,
       __webpack_require__
     ) => {
-      module.exports = __webpack_require__(900);
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/script",
+        function () {
+          return __webpack_require__(3043);
+        },
+      ]);
+      if (false) {
+      }
 
       /***/
     },
@@ -81,7 +81,7 @@
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(1984)
+      __webpack_exec__(3642)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for withRouter-HASH.js
@@ -1,34 +1,7 @@
 (self["webpackChunk_N_E"] = self["webpackChunk_N_E"] || []).push([
   [3263],
   {
-    /***/ 4631: /***/ (
-      module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      module.exports = __webpack_require__(7086);
-
-      /***/
-    },
-
-    /***/ 9216: /***/ (
-      __unused_webpack_module,
-      __unused_webpack_exports,
-      __webpack_require__
-    ) => {
-      (window.__NEXT_P = window.__NEXT_P || []).push([
-        "/withRouter",
-        function () {
-          return __webpack_require__(9803);
-        },
-      ]);
-      if (false) {
-      }
-
-      /***/
-    },
-
-    /***/ 9803: /***/ (
+    /***/ 1089: /***/ (
       __unused_webpack_module,
       __webpack_exports__,
       __webpack_require__
@@ -43,7 +16,7 @@
       /* harmony import */ var react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__ =
         __webpack_require__(5640);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1__ =
-        __webpack_require__(4631);
+        __webpack_require__(9413);
       /* harmony import */ var next_router__WEBPACK_IMPORTED_MODULE_1___default =
         /*#__PURE__*/ __webpack_require__.n(
           next_router__WEBPACK_IMPORTED_MODULE_1__
@@ -61,13 +34,40 @@
 
       /***/
     },
+
+    /***/ 3962: /***/ (
+      __unused_webpack_module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      (window.__NEXT_P = window.__NEXT_P || []).push([
+        "/withRouter",
+        function () {
+          return __webpack_require__(1089);
+        },
+      ]);
+      if (false) {
+      }
+
+      /***/
+    },
+
+    /***/ 9413: /***/ (
+      module,
+      __unused_webpack_exports,
+      __webpack_require__
+    ) => {
+      module.exports = __webpack_require__(5282);
+
+      /***/
+    },
   },
   /******/ (__webpack_require__) => {
     // webpackRuntimeModules
     /******/ var __webpack_exec__ = (moduleId) =>
       __webpack_require__((__webpack_require__.s = moduleId));
     /******/ __webpack_require__.O(0, [636, 6593, 8792], () =>
-      __webpack_exec__(9216)
+      __webpack_exec__(3962)
     );
     /******/ var __webpack_exports__ = __webpack_require__.O();
     /******/ _N_E = __webpack_exports__;
Diff for 1733-HASH.js

Diff too large to display

Diff for 4719-HASH.js

Diff too large to display

Diff for main-HASH.js

Diff too large to display

Diff for app-page-exp..ntime.dev.js
failed to diff
Diff for app-page-tur..ntime.dev.js
failed to diff
Diff for app-page-tur..ntime.dev.js
failed to diff
Diff for app-page.runtime.dev.js
failed to diff
Diff for server.runtime.prod.js

Diff too large to display

Commit: 792df26

@ijjk ijjk added the examples Issue was opened via the examples template. label May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
created-by: Next.js team PRs by the Next.js team. examples Issue was opened via the examples template. Rspack type: next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants