1. 14 Jul, 2023 4 commits
    • vercel-release-bot's avatar
      v13.4.10 · c2a54aae
      vercel-release-bot authored
      c2a54aae
    • vercel-release-bot's avatar
      v13.4.10-canary.8 · 62aa2d22
      vercel-release-bot authored
      62aa2d22
    • Shu Ding's avatar
      Fix per-entry client reference manifest for grouped and named segments (#52664) · b957f52b
      Shu Ding authored
      References for Client Components need to be aggregated to the page entry level, and emitted as files in the correct directory for the SSR server to read from. For normal routes (e.g. `app/foo/bar/page`), we can go through and collect all entries (layout, loading, error, ...) from the current and parent segments, to aggregate all necessary client references.
      
      However, for routes with special conventions like `app/(group)/@named/foo/bar/page`, it needs to be normalized (remove the named slot and group segments) so it can be grouped together with `app/(group)/@named2/foo/bar/loading`.
      b957f52b
    • Jiachi Liu's avatar
      Catch layout error in global-error (#52654) · 79227ee7
      Jiachi Liu authored
      When there's a runtime error showing in root layout (server components), it should be able to catch by `global-error`.
      
      For server components, we caught it and gonna render the error fallback components (either not-found or error page), and the response status is `200`, and since we'll display error dev overlay in developmenet mode so we only render `global-error` for production.
      
      So that you can catch more errors with `global-error` and maybe do potential error tracking on client side.
      
      Follow up of #52573
      Closes NEXT-1442
      
      minor refactor: move `appUsingSizeAdjust` into `Metadata` component so that we can just tune the flag as prop
      79227ee7
  2. 13 Jul, 2023 9 commits
  3. 12 Jul, 2023 19 commits
  4. 11 Jul, 2023 8 commits