1. 03 Nov, 2022 9 commits
    • JJ Kasper's avatar
      v13.0.2-canary.2 · 59a0d4a2
      JJ Kasper authored
      59a0d4a2
    • JJ Kasper's avatar
      Update swc builds (#42393) · 10f2c5a7
      JJ Kasper authored
      x-ref:
      https://github.com/vercel/next.js/actions/runs/3382765061/jobs/5618315815
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      10f2c5a7
    • JJ Kasper's avatar
      v13.0.2-canary.1 · f1b13d70
      JJ Kasper authored
      f1b13d70
    • JJ Kasper's avatar
      Update default eslint choice for CNA setup (#42371) · 5da108bc
      JJ Kasper authored
      This ensures we continue to default to ESLint be configured for new
      projects so that our lint checks are enabled for new projects.
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      5da108bc
    • Shu Ding's avatar
      Fix CSS modules imports not collected due to race conditions (#42392) · cd897b5c
      Shu Ding authored
      This PR fixes the bug reported by @hanneslund (reproduction:
      https://github.com/hanneslund/css-mod-import-test).
      
      There can be multiple modules with the same resource, some of them can
      be created via plugins (extracted by the mini-css plugin) and some can
      be directly transformed via loaders (e.g. the CSS modules loader). In
      these cases, we need to merge the resources generated by all of them.
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      cd897b5c
    • Ayanwola Ayomide's avatar
      update middleware cookies example (#42341) · a0f37877
      Ayanwola Ayomide authored
      in the example at ## Using Cookies, the first example, the cookie header assumption was wrong. It first confused me, before I knew it was meant to be `nextjs` instead. Thanks for building an amazing library
      
      
      
      ## 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
      - [x] 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      a0f37877
    • OJ Kwon's avatar
      feat(next/mdx): support experimental mdx-rs loader (#41919) · 5654cae2
      OJ Kwon authored
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      This PR implements a configuration option in `next.config.js` to support
      for rust-based MDX compiler (https://github.com/wooorm/mdxjs-rs).
      Currently it is marked as experimental, as mdx-rs and loader both may
      need some iteration to fix regressions.
      
      When a new experimental flag is set (`mdxRs: true`), instead of using
      `@mdx/js` loader `next/mdx` loads a new webpack loader instead.
      Internally, it mostly mimics mdx/js's loader behavior, however actual
      compilation will be delegated into next/swc's binding to call mdx-rs's
      compiler instead.
      
      I choose to use next-swc to expose its binding function, as mdx-rs
      internally uses swc already and creating new binary can double up
      bytesize (with all the complex processes of publishing new package).
      
      ## 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)
      5654cae2
    • Bryce Kalow's avatar
      fix: usage of wasm in an appDir page file using the edge runtime (#41689) · d159fb08
      Bryce Kalow authored
      
      
      Fixes #41673
      
      Updates the wasm `AssetBinding` filePath to be the fully qualified path during build so the files can get loaded.
      
      ## Bug
      
      - [x] Related issues linked using `fixes #number`
      - [x] Integration tests added
      - [x] 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)
      d159fb08
    • Tim Neutkens's avatar
      Ensure Undici is enabled for appDir in all cases (#42382) · 059538bc
      Tim Neutkens authored
      Fixes
      https://github.com/vercel/next.js/discussions/41745#discussioncomment-4040309
      
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      059538bc
  2. 02 Nov, 2022 24 commits
    • Oscar Busk's avatar
      Stop writing window specific paths in vscode configuration (#42338) · 6e442911
      Oscar Busk authored
      Vscode `tsdk` configuration handles POSIX path even on Windows, so
      there's no reason to write window-specific path to the configuration.
      
      I've always had forward slash path in `tsdk` and work on windows and in
      WSL, and that works.
      
      
      https://github.com/oBusk/npm-diff.app/blob/f71e4671430373c2af6a88c3c13f7c437334ab8d/.vscode/settings.json#L3
      
      Current solution will give a diff for people who have ran previous
      versions on windows. We could update the check to allow windows if you
      want to.
      6e442911
    • Hannes Bornö's avatar
      useSelectedLayoutSegment at the current level (#42299) · 8350f7ef
      Hannes Bornö authored
      When `useSelectedLayoutSegment` is used on the current level or in a
      page it should return null.
      
      fixes #41879
      fixes #41878
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      8350f7ef
    • Oscar Busk's avatar
      [eslint-plugin] Stop warning for head element in app/layout on Windows (#42336) · 9de871e6
      Oscar Busk authored
      ## Bug
      
      
      ![image](https://user-images.githubusercontent.com/13413409/199451248-051751e5-0a5b-4ee0-bcae-05d2933f0090.png)
      
      When trying to use app directory on Windows, the automatically created
      `Layout.tsx` get's a lint problem for having a `<head>` element.
      
      ## Solution
      
      Update the rule to check paths using `path.sep` rather than hardcoded
      `/`
      
      I also checked with `path.posix.sep` because some other rules was doing
      that (both `path.sep` and `path.posix.sep`), so I'm just following
      pattern
      9de871e6
    • Hannes Bornö's avatar
      Local font family name (#42286) · f0e768e0
      Hannes Bornö authored
      Use the name of the assigned const as the family name instead of trying
      to get it from the font file. That way we know we won't get any invalid
      characters in the font-family name.
      
      fixes #42264
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      f0e768e0
    • inokawa's avatar
      Update customizing-postcss-config.md (#42331) · 6d7c4c71
      inokawa authored
      
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      6d7c4c71
    • Shu Ding's avatar
      Add `prisma` to the external package list (#42323) · eaeb1311
      Shu Ding authored
      It uses __dirname in eval and similar things, and can't be bundled
      correctly. Hence we are adding it to the list of external packages.
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      eaeb1311
    • Dan Mindru's avatar
      Fix typo in app / hello.js template (#42335) · 503fc854
      Dan Mindru authored
      Removes the extra `}` in the url
      
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      503fc854
    • Cody Lundquist's avatar
      Fix negative lookahead example in middleware.md (#42320) · a482f068
      Cody Lundquist authored
      If you don't prefix `static` with `_next`, none of the JS will be able
      to load.
      
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      ## Documentation / Examples
      
      - [x] Make sure the linting passes by running `pnpm build && pnpm lint`
      - [x] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      a482f068
    • JJ Kasper's avatar
    • Tim Neutkens's avatar
      Ensure edge runtime doesn't propagate `cache` on fetch as Cloudflare doesn't support it. (#42362) · aef04a98
      Tim Neutkens authored
      Ensures `cache` property is removed. We'll want to move this handling
      into the `edge-runtime` package though.
      
      
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      aef04a98
    • Wyatt Johnson's avatar
      create-next-app: add head to template (#42357) · 8715fe03
      Wyatt Johnson authored
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      Added the `head.{j,t}sx` files to the `create-next-app` templates.
      8715fe03
    • JJ Kasper's avatar
      Update dev process exit handling (#42367) · 2a9e2f18
      JJ Kasper authored
      Follow-up to https://github.com/vercel/next.js/pull/42255
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      2a9e2f18
    • Alexander Kadyrov's avatar
      Fix typo in usage of onError in script.md (#42368) · 6bb8407b
      Alexander Kadyrov authored
      
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      6bb8407b
    • Delba de Oliveira's avatar
      Update getting-started.md (#42353) · 85d53718
      Delba de Oliveira authored
      Clarify that Next.js 13 can be used with the `pages` directory and that `app` features are in Beta. Link to beta docs.
      Co-authored-by: 's avatarJJ Kasper <22380829+ijjk@users.noreply.github.com>
      85d53718
    • Aleksa's avatar
      Fix typo: docs/api-reference/next/font.md (#42344) · 9f97833b
      Aleksa authored
      change typo 'Optmization' to 'Optimization'
      9f97833b
    • Marija Najdova's avatar
      Fix broken link on the upgrading guide (#42340) · 9bfd45de
      Marija Najdova authored
      I noticed this while browsing the updating guide.
      9bfd45de
    • Shu Ding's avatar
      Fix page folder being wrongly resolved as page file (#42348) · b69dac12
      Shu Ding authored
      Closes #42010.
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      b69dac12
    • Ismael's avatar
    • Jiachi Liu's avatar
      Handle dynamic css-in-js styles under suspense (#42293) · 6dbf9c32
      Jiachi Liu authored
      We insert the content returning from `useServerInsertedHTML` to head
      element for app dir, but it shouldn't only inject once since there're
      suspense boundaries that could hold insertions.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [x] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      6dbf9c32
    • Amy Burns's avatar
      Update wording to remove beta FUD and keep evergreen (#42337) · 66dc68f9
      Amy Burns authored
      
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      66dc68f9
    • AkashPattanaik's avatar
      Add `path` for information in cookie setting (#42146) · a6b40317
      AkashPattanaik authored
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      ## 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
      - [x] 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
      
      - [x] Make sure the linting passes by running `pnpm build && pnpm lint`
      - [x] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      a6b40317
    • Kiko Beats's avatar
    • Balázs Orbán's avatar
      docs(script): explain expected `next/script` behavior on client-side navigation (#42260) · 460e19f0
      Balázs Orbán authored
      This PR explains that a navigation via `Link` would not re-execute
      `next/script` components once they are added.
      
      Fixes #42111
      
      Ref: [slack
      thread](https://vercel.slack.com/archives/C02UJ0QH45Q/p1667237775929339)
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      460e19f0
    • OJ Kwon's avatar
      refactor(next/turbo): consolidate turbo devserver logic (#42315) · 76fdd256
      OJ Kwon authored
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      This PR simplifies how `--turbo` is being invoked in its napi bindings.
      After refactoring in turbopack's devserver, it is possible to reuse same
      logic between napi bindings / standalone binaries.
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      76fdd256
  3. 01 Nov, 2022 7 commits
    • JJ Kasper's avatar
      v13.0.2-canary.0 · 0c2404a4
      JJ Kasper authored
      0c2404a4
    • JJ Kasper's avatar
    • Tim Neutkens's avatar
      Add preload for layouts / components (#41519) · 1af21b51
      Tim Neutkens authored
      Preload layout/component so that fetching starts eagerly.
      <!--
      Thanks for opening a PR! Your contribution is much appreciated.
      To make sure your PR is handled as smoothly as possible we request that
      you follow the checklist sections below.
      Choose the right checklist for the change that you're making:
      -->
      
      ## 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)
      1af21b51
    • Shu Ding's avatar
    • Shu Ding's avatar
      Add sqlite3 to the default list of server externals (#42294) · fc397caa
      Shu Ding authored
      Related discussions:
      https://github.com/vercel/next.js/discussions/41745#discussioncomment-4018964
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      fc397caa
    • Wyatt Johnson's avatar
      Hybrid App Hooks Support (#41767) · 6c7e76b5
      Wyatt Johnson authored
      This adapts the new client hooks of `usePathname`, `useSearchParams`,
      and `useRouter` to work within the `pages/` directory to aid users
      attempting to migrate shared components over to the `app/` directory.
      
      > **Exception:**
      > When the pages router is not ready, `useSearchParams` will return an
      empty `URLSearchParams`. This mirrors the behavior seen in the `pages/`
      directory today in that `router.query` is not available until the client
      hydrates.
      
      This also adds a new option for `useRouter` to bring it line with the
      correct typings with the app directory. By default, calling
      `useRouter()` will return the type `NextRouter | null` to represent what
      you get when you call it from a component originating from the app
      directory. If you want to instead force it to return `NextRouter` as it
      does today, you can pass a boolean into the `useRouter` call as such:
      
      ```ts
      const router = useRouter()     // typeof router === NextRouter | null
      const router = useRouter(true) // typeof router === NextRouter
      ```
      
      This change is designed to ease the incremental adoption of app.
      6c7e76b5
    • JJ Kasper's avatar
      Update app-dir E2E tests for deploy (#42269) · b0ad8adc
      JJ Kasper authored
      x-ref:
      https://github.com/vercel/next.js/actions/runs/3364229800/jobs/5579571814
      
      ## 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 build && pnpm lint`
      - [ ] The "examples guidelines" are followed from [our contributing
      doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
      b0ad8adc