1. 16 Oct, 2022 1 commit
  2. 15 Oct, 2022 9 commits
  3. 14 Oct, 2022 8 commits
  4. 13 Oct, 2022 17 commits
  5. 12 Oct, 2022 5 commits
    • Balázs Orbán's avatar
      docs: clarify `redirects` on client-side navigation (#41362) · 46bdef81
      Balázs Orbán authored
      Ref: #41344
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      ## Feature
      
      - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      46bdef81
    • Sukka's avatar
      refactor(#41164): polyfill-module should block hydration (#41352) · 05439342
      Sukka authored
      The PR continues from #41164.
      
      `next/script` with `beforeInteractive` should not block the hydration,
      **but the `polyfill-nomodule` *should* block the hydration** (and should
      be loaded before other scripts), as `polyfill-nomodule` includes
      multiple polyfills to even execute `main-app.[hash].js` properly on old
      browsers (`Array.prototype.includes`, `String.prototype.startsWith`,
      etc.).
      
      Without `polyfill-nomodule` being loaded first, the entire
      bootstrap/hydration process might not even work on old browsers. So it
      should not be loaded through `__next_s`.
      
      cc @shuding
      Co-authored-by: 's avatarShu Ding <g@shud.in>
      05439342
    • JJ Kasper's avatar
      v12.3.2-canary.26 · 629fa8af
      JJ Kasper authored
      629fa8af
    • Tim Neutkens's avatar
      Ensure content is kept rendered below the error overlay on build errors in new router (#41360) · 3f1a61b1
      Tim Neutkens authored
      - Remove unused code
      - Keep rendering underlying component tree when there is a build error
      - Move error catch up one level
      
      
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      ## Feature
      
      - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      3f1a61b1
    • Shu Ding's avatar
      Fix CSS imports tree-shaking (#41357) · b96ff8de
      Shu Ding authored
      The way we currently track server CSS imports is to collect CSS files that each **module** depends on. This happens on the module graph level which is a global thing and cannot be tree-shaken properly (check the enabled test for more details).
      
      In this PR we collect another information, of CSS files that each **entrypoint** depends on. This is the CSS list after tree-shaken on the entry level. By intersecting these CSS imports with the module-level CSS imports, we can get the final used CSS imports for each _layout_.
      
      cc @hanneslund 
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [x] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      ## Feature
      
      - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [ ] Make sure the linting passes by running `pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      b96ff8de