Update Turbopack production test manifest #74231

vercel-release-bot · 2024-12-23T07:05:31Z

This auto-generated PR updates the production integration test manifest used when testing Turbopack.

ijjk · 2024-12-23T07:17:15Z

Stats from current PR

Default Build (Increase detected ⚠️)

General

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
buildDuration	18.8s	17.1s	N/A
buildDurationCached	16.1s	13.9s	N/A
nodeModulesSize	416 MB	416 MB	N/A
nextStartRea..uration (ms)	485ms	488ms	N/A

Client Bundles (main, webpack)

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
1187-HASH.js gzip	52.4 kB	52.4 kB	N/A
8276.HASH.js gzip	169 B	168 B	N/A
8377-HASH.js gzip	5.36 kB	5.36 kB	N/A
bccd1874-HASH.js gzip	52.8 kB	52.8 kB	N/A
framework-HASH.js gzip	57.5 kB	57.5 kB	N/A
main-app-HASH.js gzip	233 B	235 B	N/A
main-HASH.js gzip	34.1 kB	34.1 kB	N/A
webpack-HASH.js gzip	1.71 kB	1.71 kB	N/A
Overall change	0 B	0 B	✓

Legacy Client Bundles (polyfills)

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	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 update/turbopack-manifest-1734937522959	Change
_app-HASH.js gzip	193 B	193 B	✓
_error-HASH.js gzip	193 B	193 B	✓
amp-HASH.js gzip	512 B	510 B	N/A
css-HASH.js gzip	343 B	342 B	N/A
dynamic-HASH.js gzip	1.84 kB	1.84 kB	✓
edge-ssr-HASH.js gzip	265 B	265 B	✓
head-HASH.js gzip	363 B	362 B	N/A
hooks-HASH.js gzip	393 B	392 B	N/A
image-HASH.js gzip	4.49 kB	4.49 kB	N/A
index-HASH.js gzip	268 B	268 B	✓
link-HASH.js gzip	2.35 kB	2.34 kB	N/A
routerDirect..HASH.js gzip	328 B	328 B	✓
script-HASH.js gzip	397 B	397 B	✓
withRouter-HASH.js gzip	323 B	326 B	N/A
1afbb74e6ecf..834.css gzip	106 B	106 B	✓
Overall change	3.59 kB	3.59 kB	✓

Client Build Manifests

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
_buildManifest.js gzip	749 B	746 B	N/A
Overall change	0 B	0 B	✓

Rendered Page Sizes

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
index.html gzip	523 B	524 B	N/A
link.html gzip	538 B	538 B	✓
withRouter.html gzip	519 B	521 B	N/A
Overall change	538 B	538 B	✓

Edge SSR bundle Size

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
edge-ssr.js gzip	128 kB	128 kB	N/A
page.js gzip	206 kB	206 kB	N/A
Overall change	0 B	0 B	✓

Middleware size

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
middleware-b..fest.js gzip	669 B	666 B	N/A
middleware-r..fest.js gzip	155 B	156 B	N/A
middleware.js gzip	31.2 kB	31.2 kB	N/A
edge-runtime..pack.js gzip	844 B	844 B	✓
Overall change	844 B	844 B	✓

Next Runtimes

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
274-experime...dev.js gzip	322 B	322 B	✓
274.runtime.dev.js gzip	314 B	314 B	✓
app-page-exp...dev.js gzip	359 kB	359 kB	✓
app-page-exp..prod.js gzip	129 kB	129 kB	✓
app-page-tur..prod.js gzip	142 kB	142 kB	✓
app-page-tur..prod.js gzip	137 kB	137 kB	✓
app-page.run...dev.js gzip	347 kB	347 kB	✓
app-page.run..prod.js gzip	125 kB	125 kB	✓
app-route-ex...dev.js gzip	37.5 kB	37.5 kB	✓
app-route-ex..prod.js gzip	25.5 kB	25.5 kB	✓
app-route-tu..prod.js gzip	25.5 kB	25.5 kB	✓
app-route-tu..prod.js gzip	25.4 kB	25.4 kB	✓
app-route.ru...dev.js gzip	39.2 kB	39.2 kB	✓
app-route.ru..prod.js gzip	25.4 kB	25.4 kB	✓
pages-api-tu..prod.js gzip	9.69 kB	9.69 kB	✓
pages-api.ru...dev.js gzip	11.6 kB	11.6 kB	✓
pages-api.ru..prod.js gzip	9.68 kB	9.68 kB	✓
pages-turbo...prod.js gzip	21.7 kB	21.7 kB	✓
pages.runtim...dev.js gzip	27.5 kB	27.5 kB	✓
pages.runtim..prod.js gzip	21.7 kB	21.7 kB	✓
server.runti..prod.js gzip	916 kB	916 kB	✓
Overall change	2.44 MB	2.44 MB	✓

build cache Overall increase ⚠️

	vercel/next.js canary	vercel/next.js update/turbopack-manifest-1734937522959	Change
0.pack gzip	2.08 MB	2.08 MB	N/A
index.pack gzip	74 kB	74.2 kB	⚠️ +145 B
Overall change	74 kB	74.2 kB	⚠️ +145 B

Diff details

Diff for main-HASH.js

Diff too large to display

Commit: 9841836

ijjk · 2024-12-23T07:17:18Z

Failing test suites

Commit: 9841836

pnpm test-start-turbo test/production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts (turbopack)

app-dir - server-action-period-hash-custom-key > should have different manifest if the encryption key from process env is changed

Expand output

● app-dir - server-action-period-hash-custom-key › should have different manifest if the encryption key from process env is changed

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

Expected: not ["008f1c262d3399e85740ee631e51483f7b9e199431", "0081e52064757b1e34218e39676e6c7b2e5308976d"]

  18 |     expect(keysA).toEqual(keysB)
  19 |   } else {
> 20 |     expect(keysA).not.toEqual(keysB)
     |                       ^
  21 |   }
  22 | }
  23 |

  at toEqual (production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts:20:23)
  at Object.compareServerActionManifestKeys (production/app-dir/server-action-period-hash/server-action-period-hash-custom-key.test.ts:42:5)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/e2e/app-dir/next-after-app-api-usage/index.test.ts (PPR)

nextjs APIs in after() > request APIs inside after() > cannot be called in a dynamic page
nextjs APIs in after() > request APIs inside after() > cannot be called in a prerendered page > with dynamic = "error"
nextjs APIs in after() > request APIs inside after() > cannot be called in a prerendered page > with dynamic = "force-static"

Expand output

● nextjs APIs in after() › request APIs inside after() › cannot be called in a dynamic page

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

Expected substring: "[/request-apis/page-dynamic] nested cookies(): error: Error: Route /request-apis/page-dynamic used \"cookies\" inside \"after(...)\". This is not supported."
Received string:    " ○ Compiling /request-apis/page-dynamic ...
 ✓ Compiled /request-apis/page-dynamic in 11.8s (700 modules)
 GET /request-apis/page-dynamic 200 in 12832ms
[/request-apis/page-dynamic] headers(): error: Error: Route /request-apis/page-dynamic used \"headers\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"headers\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after

  at eval (../app/request-apis/helpers.js:7:19)
     5 |   after(async () => {
     6 |     try {
  >  7 |       await headers()
       |                   ^
     8 |       console.log(`[${route}] headers(): ok`)
     9 |     } catch (err) {
    10 |       console.error(`[${route}] headers(): error:`, err)
  [/request-apis/page-dynamic] cookies(): error: Error: Route /request-apis/page-dynamic used \"cookies\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"cookies\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:27:19)
  at eval (../app/request-apis/helpers.js:15:10)
    25 |   after(async () => {
    26 |     try {
  > 27 |       await cookies()
       |                   ^
    28 |       console.log(`[${route}] cookies(): ok`)
    29 |     } catch (err) {
    30 |       console.error(`[${route}] cookies(): error:`, err)
  [/request-apis/page-dynamic] connection(): error: Error: Route /request-apis/page-dynamic used \"connection\" inside \"after(...)\". The `connection()` function is used to indicate the subsequent code must only run when there is an actual Request, but \"after(...)\" executes after the request, so this function is not allowed in this scope. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:47:22)
  at eval (../app/request-apis/helpers.js:35:10)
    45 |   after(async () => {
    46 |     try {
  > 47 |       await connection()
       |                      ^
    48 |       console.log(`[${route}] connection(): ok`)
    49 |     } catch (err) {
    50 |       console.error(`[${route}] connection(): error:`, err)
  [/request-apis/page-dynamic] nested headers(): error: Error: Route /request-apis/page-dynamic used \"headers\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"headers\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:17:21)
  at eval (../app/request-apis/helpers.js:55:10)
    15 |     after(async () => {
    16 |       try {
  > 17 |         await headers()
       |                     ^
    18 |         console.log(`[${route}] nested headers(): ok`)
    19 |       } catch (err) {
    20 |         console.error(`[${route}] nested headers(): error:`, err)
  "
  at toContain (e2e/app-dir/next-after-app-api-usage/index.test.ts:72:22)
  at fn (lib/next-test-utils.ts:806:20)
  at Object.<anonymous> (e2e/app-dir/next-after-app-api-usage/index.test.ts:53:7)

● nextjs APIs in after() › request APIs inside after() › cannot be called in a prerendered page › with dynamic = "error"

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

Expected substring: "[/request-apis/page-dynamic-error] nested headers(): error: Error: Route /request-apis/page-dynamic-error used \"headers\" inside \"after(...)\". This is not supported."
Received string:    "[/request-apis/page-dynamic] nested cookies(): error: Error: Route /request-apis/page-dynamic used \"cookies\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"cookies\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after

  at eval (../app/request-apis/helpers.js:37:21)
    35 |     after(async () => {
    36 |       try {
  > 37 |         await cookies()
       |                     ^
    38 |         console.log(`[${route}] nested cookies(): ok`)
    39 |       } catch (err) {
    40 |         console.error(`[${route}] nested cookies(): error:`, err)
  [/request-apis/page-dynamic] nested connection(): error: Error: Route /request-apis/page-dynamic used \"connection\" inside \"after(...)\". The `connection()` function is used to indicate the subsequent code must only run when there is an actual Request, but \"after(...)\" executes after the request, so this function is not allowed in this scope. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:57:24)
    55 |     after(async () => {
    56 |       try {
  > 57 |         await connection()
       |                        ^
    58 |         console.log(`[${route}] nested connection(): ok`)
    59 |       } catch (err) {
    60 |         console.error(`[${route}] nested connection(): error:`, err)
   ○ Compiling /request-apis/page-dynamic-error ...
   ✓ Compiled /request-apis/page-dynamic-error in 2.3s (702 modules)
   GET /request-apis/page-dynamic-error 200 in 3652ms
  [/request-apis/page-dynamic-error] headers(): error: Error: Route /request-apis/page-dynamic-error used \"headers\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"headers\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:7:19)
     5 |   after(async () => {
     6 |     try {
  >  7 |       await headers()
       |                   ^
     8 |       console.log(`[${route}] headers(): ok`)
     9 |     } catch (err) {
    10 |       console.error(`[${route}] headers(): error:`, err)
  [/request-apis/page-dynamic-error] cookies(): error: Error: Route /request-apis/page-dynamic-error used \"cookies\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"cookies\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:27:19)
  at eval (../app/request-apis/helpers.js:15:10)
    25 |   after(async () => {
    26 |     try {
  > 27 |       await cookies()
       |                   ^
    28 |       console.log(`[${route}] cookies(): ok`)
    29 |     } catch (err) {
    30 |       console.error(`[${route}] cookies(): error:`, err)
  [/request-apis/page-dynamic-error] connection(): error: Error: Route /request-apis/page-dynamic-error used \"connection\" inside \"after(...)\". The `connection()` function is used to indicate the subsequent code must only run when there is an actual Request, but \"after(...)\" executes after the request, so this function is not allowed in this scope. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:47:22)
  at eval (../app/request-apis/helpers.js:35:10)
    45 |   after(async () => {
    46 |     try {
  > 47 |       await connection()
       |                      ^
    48 |       console.log(`[${route}] connection(): ok`)
    49 |     } catch (err) {
    50 |       console.error(`[${route}] connection(): error:`, err)
  "
  at toContain (e2e/app-dir/next-after-app-api-usage/index.test.ts:109:24)
  at fn (lib/next-test-utils.ts:806:20)
  at e2e/app-dir/next-after-app-api-usage/index.test.ts:100:9

● nextjs APIs in after() › request APIs inside after() › cannot be called in a prerendered page › with dynamic = "force-static"

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

Expected substring: "[/request-apis/page-force-static] nested connection(): error: Error: Route /request-apis/page-force-static used \"connection\" inside \"after(...)\"."
Received string:    "[/request-apis/page-dynamic-error] nested headers(): error: Error: Route /request-apis/page-dynamic-error used \"headers\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"headers\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after

  at eval (../app/request-apis/helpers.js:17:21)
  at eval (../app/request-apis/helpers.js:55:10)
    15 |     after(async () => {
    16 |       try {
  > 17 |         await headers()
       |                     ^
    18 |         console.log(`[${route}] nested headers(): ok`)
    19 |       } catch (err) {
    20 |         console.error(`[${route}] nested headers(): error:`, err)
  [/request-apis/page-dynamic-error] nested cookies(): error: Error: Route /request-apis/page-dynamic-error used \"cookies\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"cookies\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:37:21)
    35 |     after(async () => {
    36 |       try {
  > 37 |         await cookies()
       |                     ^
    38 |         console.log(`[${route}] nested cookies(): ok`)
    39 |       } catch (err) {
    40 |         console.error(`[${route}] nested cookies(): error:`, err)
  [/request-apis/page-dynamic-error] nested connection(): error: Error: Route /request-apis/page-dynamic-error used \"connection\" inside \"after(...)\". The `connection()` function is used to indicate the subsequent code must only run when there is an actual Request, but \"after(...)\" executes after the request, so this function is not allowed in this scope. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:57:24)
    55 |     after(async () => {
    56 |       try {
  > 57 |         await connection()
       |                        ^
    58 |         console.log(`[${route}] nested connection(): ok`)
    59 |       } catch (err) {
    60 |         console.error(`[${route}] nested connection(): error:`, err)
   ○ Compiling /request-apis/page-force-static ...
   ✓ Compiled /request-apis/page-force-static in 1083ms (704 modules)
   GET /request-apis/page-force-static 200 in 1221ms
  [/request-apis/page-force-static] headers(): error: Error: Route /request-apis/page-force-static used \"headers\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"headers\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:7:19)
     5 |   after(async () => {
     6 |     try {
  >  7 |       await headers()
       |                   ^
     8 |       console.log(`[${route}] headers(): ok`)
     9 |     } catch (err) {
    10 |       console.error(`[${route}] headers(): error:`, err)
  [/request-apis/page-force-static] cookies(): error: Error: Route /request-apis/page-force-static used \"cookies\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"cookies\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:27:19)
  at eval (../app/request-apis/helpers.js:15:10)
    25 |   after(async () => {
    26 |     try {
  > 27 |       await cookies()
       |                   ^
    28 |       console.log(`[${route}] cookies(): ok`)
    29 |     } catch (err) {
    30 |       console.error(`[${route}] cookies(): error:`, err)
  [/request-apis/page-force-static] connection(): error: Error: Route /request-apis/page-force-static used \"connection\" inside \"after(...)\". The `connection()` function is used to indicate the subsequent code must only run when there is an actual Request, but \"after(...)\" executes after the request, so this function is not allowed in this scope. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:47:22)
  at eval (../app/request-apis/helpers.js:35:10)
    45 |   after(async () => {
    46 |     try {
  > 47 |       await connection()
       |                      ^
    48 |       console.log(`[${route}] connection(): ok`)
    49 |     } catch (err) {
    50 |       console.error(`[${route}] connection(): error:`, err)
  [/request-apis/page-force-static] nested headers(): error: Error: Route /request-apis/page-force-static used \"headers\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"headers\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:17:21)
  at eval (../app/request-apis/helpers.js:55:10)
    15 |     after(async () => {
    16 |       try {
  > 17 |         await headers()
       |                     ^
    18 |         console.log(`[${route}] nested headers(): ok`)
    19 |       } catch (err) {
    20 |         console.error(`[${route}] nested headers(): error:`, err)
  [/request-apis/page-force-static] nested cookies(): error: Error: Route /request-apis/page-force-static used \"cookies\" inside \"after(...)\". This is not supported. If you need this data inside an \"after\" callback, use \"cookies\" outside of the callback. See more info here: https://nextjs.org/docs/canary/app/api-reference/functions/after
  at eval (../app/request-apis/helpers.js:37:21)
    35 |     after(async () => {
    36 |       try {
  > 37 |         await cookies()
       |                     ^
    38 |         console.log(`[${route}] nested cookies(): ok`)
    39 |       } catch (err) {
    40 |         console.error(`[${route}] nested cookies(): error:`, err)
  "
  at toContain (e2e/app-dir/next-after-app-api-usage/index.test.ts:129:24)
  at fn (lib/next-test-utils.ts:806:20)
  at e2e/app-dir/next-after-app-api-usage/index.test.ts:100:9

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

pnpm test-start-turbo test/production/app-dir/server-action-period-hash/server-action-period-hash.test.ts (turbopack)

app-dir - server-action-period-hash > should have same manifest between continuous two builds

Expand output

● app-dir - server-action-period-hash › should have same manifest between continuous two builds

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

- Expected  - 1
+ Received  + 1

  Array [
-   "008f1c262d3399e85740ee631e51483f7b9e199431",
    "0081e52064757b1e34218e39676e6c7b2e5308976d",
+   "008f1c262d3399e85740ee631e51483f7b9e199431",
  ]

  16 |
  17 |   if (equal) {
> 18 |     expect(keysA).toEqual(keysB)
     |                   ^
  19 |   } else {
  20 |     expect(keysA).not.toEqual(keysB)
  21 |   }

  at toEqual (production/app-dir/server-action-period-hash/server-action-period-hash.test.ts:18:19)
  at Object.compareServerActionManifestKeys (production/app-dir/server-action-period-hash/server-action-period-hash.test.ts:37:5)

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

update/turbopack-manifest-1734937522959

9841836

ijjk added CI approved Approve running CI for fork tests labels Dec 23, 2024

vercel-release-bot closed this Dec 24, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Turbopack production test manifest #74231

Update Turbopack production test manifest #74231

vercel-release-bot commented Dec 23, 2024

ijjk commented Dec 23, 2024

ijjk commented Dec 23, 2024 •

edited

Loading

Update Turbopack production test manifest #74231

Update Turbopack production test manifest #74231

Conversation

vercel-release-bot commented Dec 23, 2024

ijjk commented Dec 23, 2024

Stats from current PR

ijjk commented Dec 23, 2024 • edited Loading

Failing test suites

ijjk commented Dec 23, 2024 •

edited

Loading