1. 25 Oct, 2022 15 commits
    • JJ Kasper's avatar
      v12.3.2-canary.41 · fe5a502d
      JJ Kasper authored
      fe5a502d
    • JJ Kasper's avatar
      Fix revalidate during dev (#41772) · f2d2dde5
      JJ Kasper authored
      Fix typo `revalidate` -> `fetchRevalidate`
      f2d2dde5
    • JJ Kasper's avatar
      Add initial head handling in app (#41607) · 67c802ac
      JJ Kasper 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
      - [ ] 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)
      67c802ac
    • Jiachi Liu's avatar
      Only import dev overlay for dev mode (#41771) · e8d5de6b
      Jiachi Liu authored
      * Import dev overlay for dev mode only
      * Remove other unused code
      
      <!--
      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)
      e8d5de6b
    • Gal Schlezinger's avatar
      [typescript] fix typo in edge runtime name (#41773) · 455161cb
      Gal Schlezinger authored
      There's a typo, the `l` is missing in "experimenta**l**-edge", so this
      PR fixes it :sunglasses_+1:
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      455161cb
    • eve0415's avatar
      docs: update `ci-build-caching` (#41763) · 2ac7e4c8
      eve0415 authored
      This tiny PR is just to update document in [Continuous Integration (CI) Build Caching - GitHub Actions](https://nextjs.org/docs/advanced-features/ci-build-caching#github-actions).
      
      The last version of `actions/cache@v2` is almost an year old, which is [2.1.7](https://github.com/actions/cache/releases/tag/v2.1.7).
      It also uses [`::set-output` which is now deprecated](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/), and users should start moving to `actions/cache@v3` instead.
      
      
      As stated in [GitHub Actions: Deprecating save-state and set-output commands](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/), the deprecated method will be fully disable them on 31st May 2023, which we still have times to move.
      2ac7e4c8
    • Steven's avatar
      Throw error <a> child in <Link> (#41756) · e107bc45
      Steven authored
      This PR improves the error message when `<a>` is a child of `<Link>`
      e107bc45
    • Steven's avatar
      Bump minimum Node.js version to 14.6.0 (#41765) · a5d67423
      Steven authored
      We found a case where 14.0.0 breaking with private class methods, such
      as:
      
      ```js
      class C {
        #x() { return 42; }
        x() {
          return this.#x();
        }
      }
      ```
      
      This feature was introduced in Node.js 14.6.0, so we can bump the
      minimum version.
      
      See https://node.green
      a5d67423
    • Janicklas Ralph's avatar
      Updating avg width metrics for google fonts (#41755) · 16c7480f
      Janicklas Ralph authored
      Updating the average with using the string
      "aaabcdeeeefghiijklmnnoopqrrssttuvwxyz "
      
      <!--
      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)
      
      -->
      Co-authored-by: 's avatarHannes Bornö <hannes.borno@vercel.com>
      16c7480f
    • Hannes Bornö's avatar
      Font description and error messages (#41764) · 10e7d452
      Hannes Bornö authored
      Improve font error messages and readme
      
      ## 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)
      10e7d452
    • Jiachi Liu's avatar
      Update react next channel (#41761) · 78bf0a79
      Jiachi Liu authored
      apply react updates x-ref: https://github.com/facebook/react/pull/25560
      78bf0a79
    • Hannes Bornö's avatar
      Pathname and search params SSG (#41247) · 1d596ca9
      Hannes Bornö authored
      Bailout to client rendering when using useSearchParams and usePathName
      during SSG.
      
      ## 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)
      1d596ca9
    • Javi Velasco's avatar
      Enable appDir e2e deploy tests #1 (#41759) · 2277eb92
      Javi Velasco authored
      Enables `appDir` test for `deploy` in the `test/e2e/app-dir/index.test.ts` test suite.
      2277eb92
    • Jiachi Liu's avatar
      Dont apply existing externals path changing to rsc layers (#41744) · f5a89eb0
      Jiachi Liu authored
      We have existing rule for pages ssr that `next/dist/server` and
      `next/dist/shared` will not be bundled, but we shouldn't apply it to rsc
      layers since the they should bundle the dependencies in their own way.
      
      Adding a test that using `next/head` in the page, since head is exported
      from `next/dist/shared`, expect the page is not broken but we don't
      expect it's working
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [x] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      f5a89eb0
    • Shu Ding's avatar
      Fix edge entry layer resolution bug (#41757) · c124cabd
      Shu Ding authored
      By default the edge page entry is in the client layer because it bundles Next.js. It's a virtual loader (edge-ssr-loader) but that makes the SWC loader think the page's source is a client component.
      
      We use the resource query `__edge_ssr_entry__` to convert it to the server layer but we need to add that condition to the SWC loader too.
      
      ## 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)
      c124cabd
  2. 24 Oct, 2022 25 commits