1. 21 Sep, 2022 2 commits
  2. 20 Sep, 2022 8 commits
    • Rostyslav Melnychuk's avatar
      Updated example for i18n middleware (#40728) · 47195173
      Rostyslav Melnychuk authored
      Added support for search params and NEXT_LOCALE cookie if set
      
      <!--
      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 avatarJJ Kasper <jj@jjsweb.site>
      47195173
    • Henrik Wenz's avatar
      fix: InferGetServerSidePropsType and InferGetStaticPropsType (#40635) · 3943b20f
      Henrik Wenz authored
      ## Problem
      
      Currently the Next.js infer utility (`InferGetServerSidePropsType` and
      `InferGetStaticPropsType`) types can lead to a wrong inferred types
      (`never`). This happens if these functions return something different
      than: `{props: {}}`.
      
      **Example:** `getServerSideProps`
      
      ```typescript
      export async function getServerSideProps({ query }: GetServerSidePropsContext) {
        if (query.foo) {
          return {
            notFound: true,
          }
        }
      
        return {
          props: { 
            foo: "bar"
          },
        }
      }
      
      type PageProps = InferGetServerSidePropsType<typeof getServerSideProps>
      // => type PageProps = never
      ```
      
      **Example:** `getStaticProps`
      
      ```typescript
      import type { InferGetStaticPropsType, GetStaticPropsContext } from 'next'
      
      export async function getStaticProps(context: GetStaticPropsContext) {
        if (context.params?.bar) {
          return {
            notFound: true,
          }
        }
      
        return {
          props: {
            foo: 'bar',
          },
        }
      }
      
      type PageProps = InferGetStaticPropsType<typeof getStaticProps>
      // => type PageProps = never
      ```
      
      This is because the first infer condition of the utility type is not
      satified leading to a never result.
      
      ```typescript
      export type InferGetServerSidePropsType<T> = T extends GetServerSideProps<
        infer P, // <- NOT SATISFIED
        any
      >
        ? P
        : T extends (
            context?: GetServerSidePropsContext<any>
          ) => Promise<GetServerSidePropsResult<infer P>>
        ? P
        : never  // <- NOT SATISFIED
      ```
      
      ## Solution
      
      I have experimented with different solutions ending with a much simpler
      type, that is faster to execute, easier to read and universally usable
      for both prop variations.
      
      ```typescript
      /**
       * Flow:
       * - Make sure getStaticProps is a function
       * - Get its return type
       * - Extract the one that contains {props: any}
       * - Return the props
       */
      export type InferGetStaticPropsType<T extends (args: any) => any> = Extract<
        Awaited<ReturnType<T>>,
        { props: any }
      >['props']
      ```
      
      ## Bug
      
      - [x] Related issues: fixes #36615, #15913,
      https://twitter.com/leeerob/status/1563540593003106306
      - [x] Type tests added
      
      ## Future thoughts
      
      Since `InferGetStaticPropsType` and `InferGetServerSidePropsType` are
      now the same, it's api could be merged into one utility type (e.g:
      InferNextProps). I recommend doing this in a different PR.
      
      ## Additional info
      
      I have tested this approach using the following [external
      package](https://www.npmjs.com/package/infer-next-props-type)
      (@timneutkens sorry for the late PR). Since about 12 Month I haven't
      received any negative feedback (issues) regarding this approach.
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      3943b20f
    • Henrik Wenz's avatar
      chore: refactor with-next-sitemap example (#40712) · c2f48ea8
      Henrik Wenz authored
      ## Changes
      
      see commits
      
      ## Documentation / Examples
      
      - [x] Make sure the linting passes by running `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)
      c2f48ea8
    • Tim Neutkens's avatar
      499ce6db
    • Tim Neutkens's avatar
    • Jiachi Liu's avatar
      Use resolved url in flight entry loader (#40697) · 0fb3284d
      Jiachi Liu authored
      If there's any resolve alias in webpack config, an aliased resource url will error with `require.resolve` usage in flight manifest plugin, we need to resolve the absolute resource url first then pass down to flight manifest
      
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [x] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      0fb3284d
    • JJ Kasper's avatar
      Break assetPrefix app tests into separate suite (#40701) · 642d52e1
      JJ Kasper authored
      As discussed in slack this breaks out the `assetPrefix` tests to a
      separate suite to speed up the main `app` suite.
      
      x-ref: [slack
      thread](https://vercel.slack.com/archives/C035J346QQL/p1663623560467579)
      642d52e1
    • JJ Kasper's avatar
      Temporarily skip switchable runtime test on deploy (#40700) · e7040602
      JJ Kasper authored
      We can re-enable this after the necessary support has been landed. 
      
      x-ref:
      https://github.com/vercel/next.js/actions/runs/3086118218/jobs/4990617168
      e7040602
  3. 19 Sep, 2022 19 commits
    • JJ Kasper's avatar
      v12.3.1 · 980095d5
      JJ Kasper authored
      980095d5
    • JJ Kasper's avatar
      v12.3.1-canary.5 · 4901fc73
      JJ Kasper authored
      4901fc73
    • chornos13's avatar
      docs(examples): fix error connection handling (#40633) · a03cdc6d
      chornos13 authored
      
      
      When there's an error while connect to mongodb (timeout for example), it will be cached and need to restart next.js, by handling the error correctly (clear cached promise) it will try to reconnect to mongodb if the function is called again
      
      ## 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 avatarJJ Kasper <22380829+ijjk@users.noreply.github.com>
      a03cdc6d
    • Jiachi Liu's avatar
      Drop legacy RSC server and client extension (#40692) · 5a50a998
      Jiachi Liu authored
      Drop the support for `.server.js` and `.client.js` extension in RSC, only consume the pages with configured file extensions as page entry
      5a50a998
    • JJ Kasper's avatar
      v12.3.1-canary.4 · 35098a14
      JJ Kasper authored
      35098a14
    • Henrik Wenz's avatar
      chore: Refactor active-class-name example (#40670) · 7f9fe8ca
      Henrik Wenz authored
      ## Changes
      
      - Migrated missing file to typescript
      
      ## Documentation / Examples
      
      - [x] Make sure the linting passes by running `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)
      7f9fe8ca
    • Henrik Wenz's avatar
      chore: Migrate with-prefetching example to typescript (#40671) · 24b20dd1
      Henrik Wenz authored
      ## Documentation / Examples
      
      - [x] Make sure the linting passes by running `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)
      24b20dd1
    • Shu Ding's avatar
      Avoid direct React client API imports in the server graph (#40686) · 6279dba3
      Shu Ding authored
      We have heuristic checks in the SWC transform to make sure you are not
      using client-only APIs such as `useState` inside the Server Components
      graph. However inside our server graph compilation we also have to
      import the framework and renderer itself (not just the component), and
      some utility files import these client APIs (because they can be shared
      by the SSR or client code). Hence we have errors like
      https://github.com/vercel/next.js/actions/runs/3083270196/jobs/4984135491.
      
      To manually opt-out these errors, you can do `import React from 'react'`
      and use these APIs via `React.useState`.
      
      cc @feedthejim 
      
      ## 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)
      6279dba3
    • JJ Kasper's avatar
    • Sukka's avatar
      fix(image): preload should respect crossOrigin (#40676) · 4a53582e
      Sukka authored
      
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [x] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      
      Currently, `link[rel=preload]` inserted by `priority` will not have the `crossOrigin` attribute, which will cause the preloaded response not to be used, since the CORS policy mismatches. The PR fixes that.
      4a53582e
    • Jiachi Liu's avatar
      Remove non existed exports and files (#40685) · db3b8446
      Jiachi Liu authored
      We don't have `next/lib/data`, the entry files and types should be removed
      db3b8446
    • Jimmy Lai's avatar
      misc: update caniuse-lite to latest (#40680) · 9b0c00a5
      Jimmy Lai authored
      Fixes build errors related to
      https://github.com/browserslist/caniuse-lite/issues/102
      
      see
      https://github.com/vercel/next.js/actions/runs/3082979772/jobs/4983345078
      
      
      ## 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)
      9b0c00a5
    • Jiachi Liu's avatar
      Incldue styled-jsx in swc compiling (#40679) · ce82c60d
      Jiachi Liu authored
      Tree share the `typeof window` conditions in styled-jsx for edge runtime. Let swc loader go through the styled-jsx assets under node_modules, applying the optimization as well
      
      `test-app/server/edge-ssr.js` -155B
      ce82c60d
    • Shu Ding's avatar
      Refine error messages (#40661) · 44afc376
      Shu Ding authored
      As per @sebmarkbage's suggestion, this PR refines the error message to
      be more readable and friendly:
      
      ```
      error - ./components/qux.js
      
      You're importing a component that needs useEffect. It only works in a Client Component but none of its parents are marked with "client", so they're Server Components by default.
      
         ,----
       5 | import { useEffect } from 'react'
         :          ^^^^^^^^^
         `----
      
      Maybe one of these should be marked as a "client" entry:
      
      ./components/qux.js
      ./components/baz.js
      ./components/bar.js
      ./app/dashboard/index/page.js
      ```
      
      It's more ideal to put error codes inside the SWC transform and format
      it in the Next.js logging layer. A future improvement is to tweak the
      message a bit more for these specific cases:
      
      - [ ] The error already happens inside an entry point (page or layout),
      so itself should have "client" added (or removed), not it parents.
      - [ ] When importing `"server-only"` inside a client component, we can
      directly hint to the user which module in the import chain is marked
      with `"client"`.
      
      ## 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)
      44afc376
    • Tim Neutkens's avatar
      Upgrade to latest React experimental (#40672) · 6df87707
      Tim Neutkens authored
      Only upgrade react-exp.
      
      
      ## 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)
      6df87707
    • Tim Neutkens's avatar
    • Shu Ding's avatar
      Port page and layout level API assertions to SWC transform (#40653) · c742c038
      Shu Ding authored
      We used to do an extra pass of SWR `parse` and loop over the AST inside
      JavaScript to check if `getServerSideProps` or `getStaticProps` is used
      in a client page or layout. Instead this can be done in the same
      `react_server_components` SWC transform now.
      
      ## 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)
      c742c038
    • Tim Neutkens's avatar
      Refactor fetchServerResponse (#40674) · c7e26193
      Tim Neutkens authored
      c7e26193
    • Hannes Bornö's avatar
      Send web vitals to Vercel analytics in app (#40669) · 356b6cec
      Hannes Bornö authored
      Sends web vitals to Vercel analytics.
      
      My plan for the test was to assert the data sent by the client but there's a bug where it's always null when sending a blob https://github.com/microsoft/playwright/issues/6479.
      
      When adding support for a custom web vitals reporter it will be easier to assert the values sent by the reporter.
      356b6cec
  4. 18 Sep, 2022 5 commits
    • Tim Neutkens's avatar
      Change Flight response content type to application/octet-stream (#40665) · d41ca43d
      Tim Neutkens authored
      Ensures Flight responses are not loaded as HTML.
      
      
      ## 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)
      d41ca43d
    • Tim Neutkens's avatar
      Use createFromFetch instead of createFromReadableStream to fetch Flight (#40656) · 1bf7d4d9
      Tim Neutkens authored
      Small change leveraging the `createFromFetch` method instead.
      
      
      ## 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)
      1bf7d4d9
    • Shu Ding's avatar
      Attach module trace for RSC related errors (#40652) · 34df81e7
      Shu Ding authored
      When the error comes from the RSC transform in SWC, we want to enforce the verbose mode because the module trace can be critical here. An example:
      
      <img width="635" alt="CleanShot 2022-09-18 at 12 37 02@2x" src="https://user-images.githubusercontent.com/3676859/190898135-7b258ae1-64e4-4c7b-b4d3-b2e9d2ee0245.png">
      
      Also in this PR I changed `trace.originName` to `trace.moduleName` in the output as the former can contain loader information and options:
      
      ```
      Import trace for requested module:
      ./app/dashboard/index/page.js
      ../../../../packages/next/dist/build/webpack/loaders/next-app-loader.js?name=app%2Fdashboard%2Findex%2Fpage&appPaths=%2Fdashboard%2Findex%2Fpage&pagePath=private-next-app-dir%2Fdashboard%2Findex%2Fpage.js&appDir=%2FUsers%2Fshu%2FDocuments%2Fgit%2Fnext.js%2Ftest%2Fe2e%2Fapp-dir%2Fapp%2Fapp&pageExtensions=tsx&pageExtensions=server.tsx&pageExtensions=client.tsx&pageExtensions=ts&pageExtensions=server.ts&pageExtensions=client.ts&pageExtensions=jsx&pageExtensions=server.jsx&pageExtensions=client.jsx&pageExtensions=js&pageExtensions=server.js&pageExtensions=client.js!
      ```
      
      ## 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)
      34df81e7
    • Jiachi Liu's avatar
      Remove internal client next api detection (#40646) · 3f8f72bf
      Jiachi Liu authored
      Follow up for https://github.com/vercel/next.js/pull/40415
      
      Remove internal next client api determination, fully relying on `'client'` directive.
      Change `.client.js` extension to `.js ` in tests, remove legacy / unused test files
      3f8f72bf
    • Jiachi Liu's avatar
      Client directive (#40415) · 295f9da3
      Jiachi Liu authored
      ## Feature
      Change server components convention from using `.server.js` / `.client.js` file extension to determine it's a server or client component to using `'client'` js literal as a directive for determine client components boundary.
      React RFC: https://github.com/reactjs/rfcs/pull/189
      New behavior doesn't consume `.server.js` as server components any more, if you're enabling `serverComponents` flag, every `page.js` in app dir will become server components by default. If you adding a `'client'` directive to the page, then that page will become a client component. This rule also applies to the normal js components, client components will require a `'client'` directive to indicate its identity, instead of having a `.client.js` extension.
      - [x] 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`
      - [x] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have helpful link attached, see `contributing.md`
      Co-authored-by: 's avatarShu Ding <3676859+shuding@users.noreply.github.com>
      295f9da3
  5. 16 Sep, 2022 6 commits
    • JJ Kasper's avatar
      v12.3.1-canary.3 · f0ed328b
      JJ Kasper authored
      f0ed328b
    • JJ Kasper's avatar
      Fix edge wasm handling during deploy (#40625) · 76ae2870
      JJ Kasper authored
      This fixes the WASM handling for edge during deploy as the sandbox
      context won't be present so we should keep this restricted to dev. No
      additional tests were added as our existing tests caught this.
      
      x-ref: https://github.com/vercel/next.js/pull/39539
      Fixes:
      https://github.com/vercel/next.js/actions/runs/3049403049/jobs/4915784368
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have a helpful link attached, see `contributing.md`
      76ae2870
    • Shu Ding's avatar
      Implement SWC transformer for server and client graphs (#40603) · d5fa5558
      Shu Ding authored
      This is an initial implementation of the Server Components SWC
      transformer. For the server graph, it detects client entries via the
      `"client"` directive and transpile them into module reference code; for
      the client graph, it removes the directives. And for both graphs, it
      checks if there is any invalid imports for the given environment and
      shows proper errors.
      
      With that added, we can switch from `next-flight-client-loader` to
      directly use the SWC loader in one pass. Next step is to get rid of the
      `.client.` extension in other plugins.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Feature
      
      - [x] 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`
      - [x] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have 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.md#adding-examples)
      d5fa5558
    • Balázs Orbán's avatar
      refactor: split up `CONTRIBUTING.md` (#40515) · 3ff21ed1
      Balázs Orbán authored
      Continues #39778
      
      Closes #40499
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have 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 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.md#adding-examples)
      Co-authored-by: 's avatarTim Neutkens <tim@timneutkens.nl>
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      3ff21ed1
    • Balázs Orbán's avatar
      fix: handle `notFound: true` in `/` with `next export` (#40592) · cade8c84
      Balázs Orbán authored
      Closes #40571
      
      An earlier fix in #24481 did not consider the `/` case. The page path normalization method `normalizePagePath` turned `/` into `/index` and the route matching was skipped for the index route's non-existent HTML file.
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have 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 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.md#adding-examples)
      cade8c84
    • Janicklas Ralph's avatar
      Adding experimentalAdjustFallback feature to font optimization (#40185) · 7fba48ef
      Janicklas Ralph authored
      <!--
      
      
      ## Bug
      
      - [ ] Related issues linked using `fixes #number`
      - [ ] Integration tests added
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Feature
      
      - [x] 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`
      - [x] Integration tests added
      - [ ] Documentation added
      - [ ] Telemetry added. In case of a feature if it's used or not.
      - [ ] Errors have helpful link attached, see `contributing.md`
      
      ## Documentation / Examples
      
      - [x] 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.md#adding-examples)
      - [ ] -->
      ## Feature
      
      - [x] Implements https://github.com/vercel/next.js/discussions/40112
      - [x] Integration tests added
      
      Adds a new option to the current font optimization to enable
      experimental font size adjust
      
      The new `optimizeFonts` config will be 
      ```
      optimizeFonts: {
          inlineFonts: true,
          experimentalAdjustFallbacks: false,
        },
      ```
      
      To enable the feature, set `experimentalAdjustFallbacks: true`
      
      `optimizeFonts: false` will disable the entire feature (including
      inlining google font definition)
      Co-authored-by: 's avatarJJ Kasper <jj@jjsweb.site>
      7fba48ef