[DevOverlay] Enable new UI when PPR testing is enabled #74935

devjiwonchoi · 2025-01-15T16:22:00Z

devjiwonchoi · 2025-01-15T16:22:22Z

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

ijjk · 2025-01-15T16:25:58Z

Failing test suites

Commit: 4c613a2

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/development/app-dir/dynamic-error-trace/index.test.ts (PPR)

app dir - dynamic error trace > should show the error trace

Expand output

● app dir - dynamic error trace › should show the error trace

Expected Redbox but found none

  17 |     const browser = await next.browser('/')
  18 |
> 19 |     await assertHasRedbox(browser)
     |     ^
  20 |
  21 |     await expect(
  22 |       browser.hasElementByCssSelector(

  at Object.<anonymous> (development/app-dir/dynamic-error-trace/index.test.ts:19:5)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/development/app-dir/owner-stack-react-missing-key-prop/owner-stack-react-missing-key-prop.test.ts (PPR)

app-dir - owner-stack-react-missing-key-prop > should catch invalid element from on rsc component

Expand output

● app-dir - owner-stack-react-missing-key-prop › should catch invalid element from on rsc component

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - owner-stack-react-missing-key-prop should catch invalid element from on rsc component 1`

- Snapshot  - 1
+ Received  + 2

- at span ()
+ at span (<anonymous> (0:0))
+ at eval (app/rsc/page.tsx (7:10))
  at Page (app/rsc/page.tsx (6:13))

  41 |         `)
  42 |       } else {
> 43 |         expect(stackFramesContent).toMatchInlineSnapshot(`
     |                                    ^
  44 |           "at span ()
  45 |           at Page (app/rsc/page.tsx (6:13))"
  46 |         `)

  at Object.toMatchInlineSnapshot (development/app-dir/owner-stack-react-missing-key-prop/owner-stack-react-missing-key-prop.test.ts:43:36)

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

pnpm test-dev-turbo test/development/app-dir/capture-console-error/capture-console-error.test.ts (turbopack)

app-dir - capture-console-error > should capture browser console error and format the error message
app-dir - capture-console-error > should capture browser console error in render and dedupe if necessary
app-dir - capture-console-error > should capture browser console error in render and dedupe when multi same errors logged
app-dir - capture-console-error > should capture server replay string error from console error
app-dir - capture-console-error > should capture server replay error instance from console error
app-dir - capture-console-error > should be able to capture rsc logged error

Expand output

● app-dir - capture-console-error › should capture browser console error and format the error message

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - capture-console-error should capture browser console error and format the error message 1`

- Snapshot  - 1
+ Received  + 2

@@ -1,7 +1,8 @@
  {
-   "callStacks": "",
+   "callStacks": "onClick
+ app/browser/event/page.js (7:17)",
    "count": 1,
    "description": "trigger an console <error>",
    "source": "app/browser/event/page.js (7:17) @ onClick

     5 |     <button

  51 |
  52 |     if (process.env.TURBOPACK) {
> 53 |       expect(result).toMatchInlineSnapshot(`
     |                      ^
  54 |         {
  55 |           "callStacks": "",
  56 |           "count": 1,

  at Object.toMatchInlineSnapshot (development/app-dir/capture-console-error/capture-console-error.test.ts:53:22)

● app-dir - capture-console-error › should capture browser console error in render and dedupe if necessary

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - capture-console-error should capture browser console error in render and dedupe if necessary 1`

- Snapshot  - 1
+ Received  + 2

@@ -1,7 +1,8 @@
  {
-   "callStacks": "",
+   "callStacks": "Page
+ app/browser/render/page.js (4:11)",
    "count": 2,
    "description": "trigger an console.error in render",
    "source": "app/browser/render/page.js (4:11) @ Page

    2 |

   97 |
   98 |     if (process.env.TURBOPACK) {
>  99 |       expect(result).toMatchInlineSnapshot(`
      |                      ^
  100 |         {
  101 |           "callStacks": "",
  102 |           "count": 2,

  at Object.toMatchInlineSnapshot (development/app-dir/capture-console-error/capture-console-error.test.ts:99:22)

● app-dir - capture-console-error › should capture browser console error in render and dedupe when multi same errors logged

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - capture-console-error should capture browser console error in render and dedupe when multi same errors logged 1`

- Snapshot  - 1
+ Received  + 2

@@ -1,7 +1,8 @@
  {
-   "callStacks": "",
+   "callStacks": "Page
+ app/browser/render/page.js (4:11)",
    "count": 2,
    "description": "trigger an console.error in render",
    "source": "app/browser/render/page.js (4:11) @ Page

    2 |

  143 |
  144 |     if (process.env.TURBOPACK) {
> 145 |       expect(result).toMatchInlineSnapshot(`
      |                      ^
  146 |         {
  147 |           "callStacks": "",
  148 |           "count": 2,

  at Object.toMatchInlineSnapshot (development/app-dir/capture-console-error/capture-console-error.test.ts:145:22)

● app-dir - capture-console-error › should capture server replay string error from console error

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - capture-console-error should capture server replay string error from console error 1`

- Snapshot  - 1
+ Received  + 2

@@ -1,7 +1,8 @@
  {
-   "callStacks": "",
+   "callStacks": "Page
+ app/ssr/page.js (4:11)",
    "count": 2,
    "description": "ssr console error:client",
    "source": "app/ssr/page.js (4:11) @ Page

    2 |

  189 |
  190 |     if (process.env.TURBOPACK) {
> 191 |       expect(result).toMatchInlineSnapshot(`
      |                      ^
  192 |         {
  193 |           "callStacks": "",
  194 |           "count": 2,

  at Object.toMatchInlineSnapshot (development/app-dir/capture-console-error/capture-console-error.test.ts:191:22)

● app-dir - capture-console-error › should capture server replay error instance from console error

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - capture-console-error should capture server replay error instance from console error 1`

- Snapshot  - 1
+ Received  + 2

@@ -1,7 +1,8 @@
  {
-   "callStacks": "",
+   "callStacks": "Page
+ app/ssr-error-instance/page.js (4:17)",
    "count": 2,
    "description": "Error: page error",
    "source": "app/ssr-error-instance/page.js (4:17) @ Page

    2 |

  235 |
  236 |     if (process.env.TURBOPACK) {
> 237 |       expect(result).toMatchInlineSnapshot(`
      |                      ^
  238 |         {
  239 |           "callStacks": "",
  240 |           "count": 2,

  at Object.toMatchInlineSnapshot (development/app-dir/capture-console-error/capture-console-error.test.ts:237:22)

● app-dir - capture-console-error › should be able to capture rsc logged error

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - capture-console-error should be able to capture rsc logged error 1`

- Snapshot  - 1
+ Received  + 3

@@ -1,7 +1,9 @@
  {
-   "callStacks": "JSON.parse
+   "callStacks": "Page
+ app/rsc/page.js (2:17)
+ JSON.parse
  <anonymous> (0:0)",
    "count": 1,
    "description": "[ Server ] Error: boom",
    "source": "app/rsc/page.js (2:17) @ Page
  ↵

  281 |
  282 |     if (process.env.TURBOPACK) {
> 283 |       expect(result).toMatchInlineSnapshot(`
      |                      ^
  284 |         {
  285 |           "callStacks": "JSON.parse
  286 |         <anonymous> (0:0)",

  at Object.toMatchInlineSnapshot (development/app-dir/capture-console-error/capture-console-error.test.ts:283:22)

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

pnpm test-dev test/development/app-dir/owner-stack-react-missing-key-prop/react-missing-key-prop.test.ts

app-dir - react-missing-key-prop > should catch invalid element from on rsc component
app-dir - react-missing-key-prop > should catch invalid element from on ssr client component

Expand output

● app-dir - react-missing-key-prop › should catch invalid element from on rsc component

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - react-missing-key-prop should catch invalid element from on rsc component 1`

Snapshot: ""
Received: "at Page (app/rsc/page.tsx (5:6))"

  75 |         `)
  76 |       } else {
> 77 |         expect(stackFramesContent).toMatchInlineSnapshot(`""`)
     |                                    ^
  78 |         expect(source).toMatchInlineSnapshot(`
  79 |                  "app/rsc/page.tsx (5:6) @ Page
  80 |

  at Object.toMatchInlineSnapshot (development/app-dir/owner-stack-react-missing-key-prop/react-missing-key-prop.test.ts:77:36)

● app-dir - react-missing-key-prop › should catch invalid element from on ssr client component

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - react-missing-key-prop should catch invalid element from on ssr client component 1`

Snapshot: ""
Received: "at Page (app/ssr/page.tsx (7:6))"

  110 |               `)
  111 |       } else {
> 112 |         expect(stackFramesContent).toMatchInlineSnapshot(`""`)
      |                                    ^
  113 |         expect(source).toMatchInlineSnapshot(`
  114 |                  "app/ssr/page.tsx (7:6) @ Page
  115 |

  at Object.toMatchInlineSnapshot (development/app-dir/owner-stack-react-missing-key-prop/react-missing-key-prop.test.ts:112:36)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/development/app-dir/serialize-circular-error/serialize-circular-error.test.ts (PPR)

serialize-circular-error > should serialize the object from server component in console correctly

Expand output

● serialize-circular-error › should serialize the object from server component in console correctly

Expected Redbox but found none

  13 |   it('should serialize the object from server component in console correctly', async () => {
  14 |     const browser = await next.browser('/')
> 15 |     await assertHasRedbox(browser)
     |     ^
  16 |
  17 |     const description = await getRedboxDescription(browser)
  18 |     // React cannot serialize thrown objects with circular references

  at Object.<anonymous> (development/app-dir/serialize-circular-error/serialize-circular-error.test.ts:15:5)

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

pnpm test-dev-turbo test/development/app-dir/owner-stack/owner-stack.test.ts (turbopack)

app-dir - owner-stack > should log stitched error for browser uncaught errors
app-dir - owner-stack > should log stitched error for browser caught errors
app-dir - owner-stack > should log stitched error for SSR errors

Expand output

● app-dir - owner-stack › should log stitched error for browser uncaught errors

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - owner-stack should log stitched error for browser uncaught errors 1`

- Snapshot  - 0
+ Received  + 1

+ at useThrowError (app/browser/uncaught/page.js (5:11))
  at useErrorHook (app/browser/uncaught/page.js (10:3))
  at Page (app/browser/uncaught/page.js (14:3))

  56 |
  57 |     const stackFramesContent = await getStackFramesContent(browser)
> 58 |     expect(stackFramesContent).toMatchInlineSnapshot(`
     |                                ^
  59 |        "at useErrorHook (app/browser/uncaught/page.js (10:3))
  60 |        at Page (app/browser/uncaught/page.js (14:3))"
  61 |       `)

  at Object.toMatchInlineSnapshot (development/app-dir/owner-stack/owner-stack.test.ts:58:32)

● app-dir - owner-stack › should log stitched error for browser caught errors

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - owner-stack should log stitched error for browser caught errors 1`

- Snapshot  - 0
+ Received  + 1

+ at useThrowError (app/browser/caught/page.js (34:11))
  at useErrorHook (app/browser/caught/page.js (39:3))
  at Thrower (app/browser/caught/page.js (29:3))
  at Inner (app/browser/caught/page.js (23:7))
  at Page (app/browser/caught/page.js (43:10))

  121 |     const stackFramesContent = await getStackFramesContent(browser)
  122 |     if (isTurbopack) {
> 123 |       expect(stackFramesContent).toMatchInlineSnapshot(`
      |                                  ^
  124 |        "at useErrorHook (app/browser/caught/page.js (39:3))
  125 |        at Thrower (app/browser/caught/page.js (29:3))
  126 |        at Inner (app/browser/caught/page.js (23:7))

  at Object.toMatchInlineSnapshot (development/app-dir/owner-stack/owner-stack.test.ts:123:34)

● app-dir - owner-stack › should log stitched error for SSR errors

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `app-dir - owner-stack should log stitched error for SSR errors 1`

- Snapshot  - 0
+ Received  + 1

+ at useThrowError (app/ssr/page.js (4:9))
  at useErrorHook (app/ssr/page.js (8:3))
  at Page (app/ssr/page.js (12:3))

  162 |
  163 |     const stackFramesContent = await getStackFramesContent(browser)
> 164 |     expect(stackFramesContent).toMatchInlineSnapshot(`
      |                                ^
  165 |         "at useErrorHook (app/ssr/page.js (8:3))
  166 |         at Page (app/ssr/page.js (12:3))"
  167 |       `)

  at Object.toMatchInlineSnapshot (development/app-dir/owner-stack/owner-stack.test.ts:164:32)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/development/app-dir/prerender-indicator/prerender-indicator.test.ts (PPR)

prerender indicator > should have prerender-indicator by default for static page

Expand output

● prerender indicator › should have prerender-indicator by default for static page

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

Expected: true
Received: false

  23 |
  24 |     await retry(async () => {
> 25 |       expect(await hasStaticIndicator(browser)).toBe(true)
     |                                                 ^
  26 |     })
  27 |   })
  28 |

  at toBe (development/app-dir/prerender-indicator/prerender-indicator.test.ts:25:49)
  at retry (lib/next-test-utils.ts:806:14)
  at Object.<anonymous> (development/app-dir/prerender-indicator/prerender-indicator.test.ts:24:5)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/e2e/app-dir/global-error/with-style-import/index.test.ts (PPR)

app dir - global error - with style import > should render global error with correct styles

Expand output

● app dir - global error - with style import › should render global error with correct styles

Expected Redbox but found none

  3 |
  4 | async function testDev(browser, errorRegex) {
> 5 |   await assertHasRedbox(browser)
    |   ^
  6 |   expect(await getRedboxHeader(browser)).toMatch(errorRegex)
  7 | }
  8 |

  at testDev (e2e/app-dir/global-error/with-style-import/index.test.ts:5:3)
  at Object.<anonymous> (e2e/app-dir/global-error/with-style-import/index.test.ts:23:7)

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

__NEXT_EXPERIMENTAL_PPR=true pnpm test-dev test/development/app-dir/server-navigation-error/server-navigation-error.test.ts (PPR)

server-navigation-error > middleware > should error on navigation API redirect
server-navigation-error > middleware > should error on navigation API not-found
server-navigation-error > pages router > should error on navigation API redirect
server-navigation-error > pages router > should error on navigation API notFound

Expand output

● server-navigation-error › pages router › should error on navigation API redirect

Expected Redbox but found none

  14 |     it('should error on navigation API redirect', async () => {
  15 |       const browser = await next.browser('/pages/redirect')
> 16 |       await assertHasRedbox(browser)
     |       ^
  17 |       expect(await getRedboxDescription(browser)).toMatch(
  18 |         `Next.js navigation API is not allowed to be used in Pages Router.`
  19 |       )

  at Object.<anonymous> (development/app-dir/server-navigation-error/server-navigation-error.test.ts:16:7)

● server-navigation-error › pages router › should error on navigation API notFound

Expected Redbox but found none

  46 |     it('should error on navigation API notFound', async () => {
  47 |       const browser = await next.browser('/pages/not-found')
> 48 |       await assertHasRedbox(browser)
     |       ^
  49 |       expect(await getRedboxDescription(browser)).toMatch(
  50 |         `Next.js navigation API is not allowed to be used in Pages Router.`
  51 |       )

  at Object.<anonymous> (development/app-dir/server-navigation-error/server-navigation-error.test.ts:48:7)

● server-navigation-error › middleware › should error on navigation API redirect

Expected Redbox but found none

  82 |       // FIXME: the first request to middleware error load didn't show the redbox, need one more reload
  83 |       await browser.refresh()
> 84 |       await assertHasRedbox(browser)
     |       ^
  85 |       expect(await getRedboxDescription(browser)).toMatch(
  86 |         `Next.js navigation API is not allowed to be used in Middleware.`
  87 |       )

  at Object.<anonymous> (development/app-dir/server-navigation-error/server-navigation-error.test.ts:84:7)

● server-navigation-error › middleware › should error on navigation API not-found

Expected Redbox but found none

  116 |     it('should error on navigation API not-found', async () => {
  117 |       const browser = await next.browser('/middleware/not-found')
> 118 |       await assertHasRedbox(browser)
      |       ^
  119 |       expect(await getRedboxDescription(browser)).toMatch(
  120 |         `Next.js navigation API is not allowed to be used in Middleware.`
  121 |       )

  at Object.<anonymous> (development/app-dir/server-navigation-error/server-navigation-error.test.ts:118:7)

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

pnpm test-dev test/e2e/app-dir/non-root-project-monorepo/non-root-project-monorepo.test.ts

non-root-project-monorepo > source-maps > should work on RSC
non-root-project-monorepo > source-maps > should work on SSR
non-root-project-monorepo > source-maps > should work on client-side

Expand output

● non-root-project-monorepo › source-maps › should work on RSC

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `non-root-project-monorepo source-maps should work on RSC 2`

- Snapshot  - 0
+ Received  + 2

@@ -1,5 +1,7 @@
+ eval
+ app/separate-file.ts (1:11)
  <unknown>
  rsc)/./app/separate-file.ts (rsc://React/Server/file://<full-path>/apps/web/.next/server/app/source-maps-rsc/page.js
  __webpack_require__
  file://<full-path>/apps/web/.next/server/webpack-runtime.js
  innerArrowFunction

  134 |           // TODO webpack runtime code shouldn't be included in stack trace
  135 |           expect(normalizeStackTrace(await getRedboxCallStack(browser)))
> 136 |             .toMatchInlineSnapshot(`
      |              ^
  137 |            "<unknown>
  138 |            rsc)/./app/separate-file.ts (rsc://React/Server/file://<full-path>/apps/web/.next/server/app/source-maps-rsc/page.js
  139 |            __webpack_require__

  at Object.toMatchInlineSnapshot (e2e/app-dir/non-root-project-monorepo/non-root-project-monorepo.test.ts:136:14)

● non-root-project-monorepo › source-maps › should work on SSR

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `non-root-project-monorepo source-maps should work on SSR 2`

- Snapshot  - 0
+ Received  + 2

@@ -1,5 +1,7 @@
+ eval
+ app/separate-file.ts (1:7)
  ./app/separate-file.ts
  file://<full-path>/apps/web/.next/static/chunks/app/source-maps-ssr/page.js (27:1)
  options.factory
  file://<full-path>/apps/web/.next/static/chunks/webpack.js (700:31)
  __webpack_require__

  183 |           // TODO webpack runtime code shouldn't be included in stack trace
  184 |           expect(normalizeStackTrace(await getRedboxCallStack(browser)))
> 185 |             .toMatchInlineSnapshot(`
      |              ^
  186 |            "./app/separate-file.ts
  187 |            file://<full-path>/apps/web/.next/static/chunks/app/source-maps-ssr/page.js (27:1)
  188 |            options.factory

  at Object.toMatchInlineSnapshot (e2e/app-dir/non-root-project-monorepo/non-root-project-monorepo.test.ts:185:14)

● non-root-project-monorepo › source-maps › should work on client-side

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `non-root-project-monorepo source-maps should work on client-side 2`

- Snapshot  - 0
+ Received  + 2

@@ -1,5 +1,7 @@
+ eval
+ app/separate-file.ts (1:7)
  ./app/separate-file.ts
  file://<full-path>/apps/web/.next/static/chunks/app/source-maps-client/page.js (27:1)
  options.factory
  file://<full-path>/apps/web/.next/static/chunks/webpack.js (712:31)
  __webpack_require__

  236 |           // TODO webpack runtime code shouldn't be included in stack trace
  237 |           expect(normalizeStackTrace(await getRedboxCallStack(browser)))
> 238 |             .toMatchInlineSnapshot(`
      |              ^
  239 |            "./app/separate-file.ts
  240 |            file://<full-path>/apps/web/.next/static/chunks/app/source-maps-client/page.js (27:1)
  241 |            options.factory

  at Object.toMatchInlineSnapshot (e2e/app-dir/non-root-project-monorepo/non-root-project-monorepo.test.ts:238:14)

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

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

ReactRefreshLogBox turbo > should show anonymous frames from stack trace
ReactRefreshLogBox turbo > should collapse nodejs internal stack frames from stack trace

Expand output

● ReactRefreshLogBox turbo › should show anonymous frames from stack trace

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `ReactRefreshLogBox turbo should show anonymous frames from stack trace 1`

- Snapshot  - 0
+ Received  + 1

+ at <unknown> (pages/index.js (3:11))
  at Array.map ()
  at Page (pages/index.js (2:13))

  794 |
  795 |     const stack = await getStackFramesContent(browser)
> 796 |     expect(stack).toMatchInlineSnapshot(`
      |                   ^
  797 |      "at Array.map ()
  798 |      at Page (pages/index.js (2:13))"
  799 |     `)

  at Object.toMatchInlineSnapshot (development/acceptance/ReactRefreshLogBox.test.ts:796:19)

● ReactRefreshLogBox turbo › should collapse nodejs internal stack frames from stack trace

expect(received).toMatchInlineSnapshot(snapshot)

Snapshot name: `ReactRefreshLogBox turbo should collapse nodejs internal stack frames from stack trace 1`

- Snapshot  - 0
+ Received  + 1

+ at createURL (pages/index.js (4:3))
  at getServerSideProps (pages/index.js (8:3))

  825 |
  826 |     const stack = await getStackFramesContent(browser)
> 827 |     expect(stack).toMatchInlineSnapshot(
      |                   ^
  828 |       `"at getServerSideProps (pages/index.js (8:3))"`
  829 |     )
  830 |

  at Object.toMatchInlineSnapshot (development/acceptance/ReactRefreshLogBox.test.ts:827:19)

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

ijjk · 2025-01-15T16:29:58Z

Stats from current PR

Default Build (Increase detected ⚠️)

General Overall increase ⚠️

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
buildDuration	18.6s	15.5s	N/A
buildDurationCached	14.7s	12.1s	N/A
nodeModulesSize	418 MB	418 MB	⚠️ +47.8 kB
nextStartRea..uration (ms)	396ms	397ms	N/A

Client Bundles (main, webpack)

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
5306-HASH.js gzip	54 kB	54 kB	N/A
8276.HASH.js gzip	169 B	168 B	N/A
8377-HASH.js gzip	5.44 kB	5.44 kB	N/A
bccd1874-HASH.js gzip	52.9 kB	52.9 kB	✓
framework-HASH.js gzip	57.5 kB	57.5 kB	N/A
main-app-HASH.js gzip	240 B	242 B	N/A
main-HASH.js gzip	34.3 kB	34.3 kB	N/A
webpack-HASH.js gzip	1.71 kB	1.71 kB	N/A
Overall change	52.9 kB	52.9 kB	✓

Legacy Client Bundles (polyfills)

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	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 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	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.57 kB	4.57 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 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
_buildManifest.js gzip	749 B	747 B	N/A
Overall change	0 B	0 B	✓

Rendered Page Sizes

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
index.html gzip	522 B	524 B	N/A
link.html gzip	538 B	537 B	N/A
withRouter.html gzip	519 B	520 B	N/A
Overall change	0 B	0 B	✓

Edge SSR bundle Size

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
edge-ssr.js gzip	129 kB	129 kB	N/A
page.js gzip	208 kB	208 kB	N/A
Overall change	0 B	0 B	✓

Middleware size

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
middleware-b..fest.js gzip	668 B	665 B	N/A
middleware-r..fest.js gzip	155 B	156 B	N/A
middleware.js gzip	31.3 kB	31.3 kB	N/A
edge-runtime..pack.js gzip	844 B	844 B	✓
Overall change	844 B	844 B	✓

Next Runtimes

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	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	374 kB	373 kB	N/A
app-page-exp..prod.js gzip	130 kB	130 kB	✓
app-page-tur..prod.js gzip	143 kB	143 kB	✓
app-page-tur..prod.js gzip	139 kB	139 kB	✓
app-page.run...dev.js gzip	362 kB	361 kB	N/A
app-page.run..prod.js gzip	126 kB	126 kB	✓
app-route-ex...dev.js gzip	37.6 kB	37.6 kB	✓
app-route-ex..prod.js gzip	25.6 kB	25.6 kB	✓
app-route-tu..prod.js gzip	25.6 kB	25.6 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.8 kB	21.8 kB	✓
pages.runtim...dev.js gzip	27.6 kB	27.6 kB	✓
pages.runtim..prod.js gzip	21.8 kB	21.8 kB	✓
server.runti..prod.js gzip	916 kB	916 kB	✓
Overall change	1.74 MB	1.74 MB	✓

build cache Overall increase ⚠️

	vercel/next.js canary	vercel/next.js 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled	Change
0.pack gzip	2.09 MB	2.09 MB	N/A
index.pack gzip	74.7 kB	75.3 kB	⚠️ +557 B
Overall change	74.7 kB	75.3 kB	⚠️ +557 B

Diff details

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.runtime.dev.js

failed to diff

Commit: 4c613a2

ijjk added created-by: Next.js team PRs by the Next.js team. type: next labels Jan 15, 2025

This was referenced Jan 15, 2025

[DevOverlay] Fix floating header invisble on small screen #74886

Merged

[DevOverlay] Keep pagination on Build Error #74905

Merged

devjiwonchoi mentioned this pull request Jan 15, 2025

[DevOverlay] Gather Feedback per Error #74908

Merged

ijjk added the tests label Jan 16, 2025

devjiwonchoi force-pushed the 01-15-_devoverlay_gather_feedback_per_error branch 3 times, most recently from 279cbd2 to 003a61d Compare January 16, 2025 16:43

devjiwonchoi changed the base branch from 01-15-_devoverlay_gather_feedback_per_error to graphite-base/74935 January 16, 2025 17:00

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch from 7d9c834 to f477735 Compare January 16, 2025 17:13

devjiwonchoi force-pushed the graphite-base/74935 branch from 003a61d to 4a0c516 Compare January 16, 2025 17:13

devjiwonchoi changed the base branch from graphite-base/74935 to canary January 16, 2025 17:13

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch from f477735 to ee2754d Compare January 16, 2025 17:18

devjiwonchoi mentioned this pull request Jan 16, 2025

[DevOverlay] Decouple Error Overlay with DevTools Indicator #74999

Open

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch from ee2754d to 7c8e142 Compare January 16, 2025 19:32

devjiwonchoi changed the base branch from canary to 01-17-_devoverlay_decouple_error_overlay_with_devtools_indicator January 16, 2025 19:32

devjiwonchoi mentioned this pull request Jan 16, 2025

[DevOverlay] Rename file names to kebab #75000

Merged

devjiwonchoi force-pushed the 01-17-_devoverlay_decouple_error_overlay_with_devtools_indicator branch from c671e8a to ddf157e Compare January 16, 2025 21:14

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch from 7c8e142 to 7b6ba6e Compare January 16, 2025 21:14

devjiwonchoi force-pushed the 01-17-_devoverlay_decouple_error_overlay_with_devtools_indicator branch 2 times, most recently from 970daea to 8bea48c Compare January 16, 2025 21:40

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch from 7b6ba6e to e6d41c4 Compare January 16, 2025 21:40

devjiwonchoi force-pushed the 01-17-_devoverlay_decouple_error_overlay_with_devtools_indicator branch from 8bea48c to ac0f76f Compare January 17, 2025 00:38

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch 2 times, most recently from 6649e86 to f2f1850 Compare January 17, 2025 00:52

devjiwonchoi force-pushed the 01-17-_devoverlay_decouple_error_overlay_with_devtools_indicator branch from 0d43d19 to 05b4b00 Compare January 17, 2025 08:53

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch 2 times, most recently from 58e767c to 99fbf39 Compare January 17, 2025 09:09

devjiwonchoi changed the base branch from 01-17-_devoverlay_decouple_error_overlay_with_devtools_indicator to 01-17-_devoverlay_open_error_overlay_when_devtools_indicator_clicked January 17, 2025 09:09

devjiwonchoi mentioned this pull request Jan 17, 2025

[DevOverlay] Open Error Overlay when DevTools Indicator clicked #75025

Open

[DevOverlay] Enable new UI when PPR testing is enabled

ee226a6

devjiwonchoi force-pushed the 01-17-_devoverlay_open_error_overlay_when_devtools_indicator_clicked branch from 5820d4d to 39be163 Compare January 17, 2025 09:21

devjiwonchoi force-pushed the 01-16-_devoverlay_enable_new_ui_when_ppr_testing_is_enabled branch from 99fbf39 to ee226a6 Compare January 17, 2025 09:21

devjiwonchoi added 5 commits January 17, 2025 18:43

update invalid-element-type snapshot

2ebeaa8

owner-stack-invalid-element-type snapshot turbo

61ad0f8

capture console error owner stack

d3c89d0

error-ignored-frames

d6d2b2e

owner-stack-react-missing-key-prop

4c613a2

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[DevOverlay] Enable new UI when PPR testing is enabled #74935

[DevOverlay] Enable new UI when PPR testing is enabled #74935

devjiwonchoi commented Jan 15, 2025 •

edited

Loading

devjiwonchoi commented Jan 15, 2025 •

edited

Loading

ijjk commented Jan 15, 2025 •

edited

Loading

ijjk commented Jan 15, 2025 •

edited

Loading

[DevOverlay] Enable new UI when PPR testing is enabled #74935

Are you sure you want to change the base?

[DevOverlay] Enable new UI when PPR testing is enabled #74935

Conversation

devjiwonchoi commented Jan 15, 2025 • edited Loading

devjiwonchoi commented Jan 15, 2025 • edited Loading

ijjk commented Jan 15, 2025 • edited Loading

Failing test suites

ijjk commented Jan 15, 2025 • edited Loading

Stats from current PR

devjiwonchoi commented Jan 15, 2025 •

edited

Loading

devjiwonchoi commented Jan 15, 2025 •

edited

Loading

ijjk commented Jan 15, 2025 •

edited

Loading

ijjk commented Jan 15, 2025 •

edited

Loading