skills/vercel__next.js
1
0
Fork 0
mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00
Code Issues Packages Projects Releases Wiki Activity
35,737 Commits 2,682 Branches 4,056 Tags
codex/improve-agent-feedback-protocol
Commit Graph

3804 Commits

Author SHA1 Message Date
Kid de7e13e5eb Remove incorrect PostCSS config type (#81338) 
### What?

Currently the docs is incorrectly suggesting to type the PostCSS config
with types from Tailwind CSS. This pull request removed the wrong types.

If desired one can correctly type the config with the
[`postcss-load-config`](https://github.com/postcss/postcss-load-config/blob/main/src/index.d.ts#L52-L60)
package:

```js
/** @type {import('postcss-load-config').Config} */
const config = {
    plugins: {
        '@tailwindcss/postcss': {},
    },
}

export default config
```

However if your package manager does not hoist the package, you need to
install it separately just for the types, which does not seem to be
worth it.

### Why?

### How?

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-07-05 23:17:10 +00:00
Raj Kumar Rawat 6b5c9548f6 fix(docs): correct section count from 4 to 3 in intro (#81323) 
The docs mention 4 sections but only list 3: Getting Started, Guides,
and API Reference.

This updates the "How to use the docs" section to correctly reflect that
only 3 sections are listed, not 4.

**Before:**
The docs are organized into 4 sections:

**After:**
The docs are organized into 3 sections:

Let me know if a fourth section was intended to be included instead.


<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-07-05 23:14:14 +00:00
Sajad Torkamani 6ba9c21d29 fix typo (#81336) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
 2025-07-05 22:54:02 +00:00
mm c28261568f Update caching.mdx (#81185) 
Updating caching guide to be more specific on fetch API. Solves
https://github.com/vercel/next.js/issues/81183

<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

---------

Co-authored-by: Joseph <sephxd1234@gmail.com>
Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-07-03 12:45:47 +02:00
Ethan Niser 4551373c97 Docs: include effect in docs for default optimized libraries (#81203) 
This PR updates the docs for `optimizePackageImports` default optimized
packages to include `effect` and the `@effect/*` packages

These were added by 9f647f311f 

<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-07-03 09:38:48 +00:00
Joseph 82115d6e5e Docs/after function mdx fix (#81174) 
The current formatting caused the mdx parser to do `details > p >
summary` - which caused a hydration error for invalid HTML, but also
just rendered `> Details`

<img width="501" alt="Screenshot 2025-07-02 at 10 38 51"
src="https://github.com/user-attachments/assets/61819edc-75bb-4824-a000-71a4dc880905"
/>

After:

<img width="481" alt="Screenshot 2025-07-02 at 10 47 23"
src="https://github.com/user-attachments/assets/d42c2087-ce78-4944-a580-e4630cfa864d"
/>
 2025-07-03 10:44:21 +02:00
Joseph fbc988d042 docs: Getting started pages and search params (#80616) 
Closes:
https://linear.app/vercel/issue/DOC-4789/getting-started-layout-and-pages-search-params

---------

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
 2025-07-03 09:07:29 +02:00
Marek Lisy 5efef45226 Update caching.mdx (#81129) 
### What?

Fix misleading information in the docs about mixing cached and uncached
`fetch` calls during dynamic rendering.

### Why?

I followed the guide (using Next.js 15.3.2) and tried it out with this
code:
```ts
  const joke = await fetch("https://api.chucknorris.io/jokes/random", {
    cache: "no-cache",
  });
  const jokeData = await joke.json();

  console.log("Fetched joke:", jokeData.value);

  const joke2 = await fetch(
    "https://api.chucknorris.io/jokes/random?category=dev"
  );
  const jokeData2 = await joke2.json();
  console.log("Fetched joke2:", jokeData2.value);
```

After building and starting the production server, when I refresh the
page, both `jokeData.value` and `jokeData2.value` are different,
uncached. If I want the other `fetch` to be cached, I need to explicitly
enable caching, e.g.

```ts
  const joke = await fetch("https://api.chucknorris.io/jokes/random", {
    cache: "no-cache",
  });
  const jokeData = await joke.json();

  console.log("Fetched joke:", jokeData.value);

  const joke2 = await fetch(
    "https://api.chucknorris.io/jokes/random?category=dev",
    {
      cache: "force-cache",
    }
  );
  const jokeData2 = await joke2.json();
  console.log("Fetched joke2:", jokeData2.value);
```

This way the first fetch is not cached while the second one is.

### How?

The previous version claimed:
> Other `fetch` requests that do not opt out of caching will still be
cached in the Data Cache.

But below in the guide, we can see this:
> The default caching behavior of fetch (e.g., when the cache option is
not specified) is equal to setting the cache option to no-store:

So the first citation is misleading - the fetch requests are not cached
by default (with dynamic rendering - static rendering would cache the
single call it into the output), so we actually need to explicitly
enable caching to have them cached.

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-07-02 09:56:02 +02:00
adrian acosta dd374da668 Docs: moved table for Unsupported Metadata to the correct location (#80979) 
The table used for Unsupported Metadata was misplaced, so I moved it.

Next.js Docs page:
https://nextjs.org/docs/app/api-reference/functions/generate-metadata#unsupported-metadata

The section for 'Unsupported Metadata':

![Screenshot_26-6-2025_183814_nextjs
org](https://github.com/user-attachments/assets/a265678c-8330-47cd-bf02-93cc23a9c713)

The misplaced table (located a few sections down):

![Screenshot_26-6-2025_183914_nextjs
org](https://github.com/user-attachments/assets/86ea5c75-4bce-4f50-a2e1-aa8af6a01529)

---------

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-07-01 20:56:31 +02:00
Joseph ce553744b5 Docs: paper cuts July 1st (#81109) 
Just a couple of adjustments to Caching docs claim that React State is
preserved upon SPA transitions - as of today, without the Activity API,
only shared layouts state is preserved.

And we are saying redirect should be called outside try/catch blocks,
but rather, it is the try block that's the problem. So I am rephrasing
that.

I still think it is best to keep the redirect away from the try/catch
statement altogether.
 2025-07-01 13:20:17 +02:00
Exotic 80a580573e docs: fix grammatical error in upgrading to v15 guide (#81038) 
Title is pretty self descriptive.

<img width="667" alt="image"
src="https://github.com/user-attachments/assets/211f9eee-5d39-494e-abb9-9cad996b75be"
/>

Removes the word "you" for better grammatical clarity.

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-07-01 10:48:47 +02:00
Joseph 52a761e652 chore: .ts ext is most commonly used for middleware and routes (#81059) 
`middleware.ts` and `route.ts` are commonly used
 2025-06-30 13:28:48 +02:00
Mohammed 3327565c43 docs(fetch): update wording on conflicting cache and revalidate options (#80591) 
Clarifies that using conflicting options such as `{ revalidate: 3600,
cache: 'no-store' }` results in a warning in the terminal rather than an
error.

This change helps accurately reflect the current runtime behavior and
avoids misleading readers into expecting a hard failure.

The update improves developer understanding when configuring fetch/cache
strategies in their applications.

---------

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-06-30 10:12:38 +02:00
Tim Neutkens e0a7a95fb2 Turbopack: @next/mdx extension option is supported (#81058) 
## What?

@wbinnssmith added support for this option some time ago.
 2025-06-30 09:41:18 +02:00
Luciano Mammino 812596e77e Update backend-for-frontend.mdx (#80942) 
Example function in [App Router > Guides > Backend For Frontend > Public
Endpoints](https://nextjs.org/docs/app/guides/backend-for-frontend#public-endpoints)
should be `async` (since using `await`)

<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

---------

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-06-26 20:08:22 +02:00
Joseph 166f710c1f Docs/feedback june batch (#80651) 
Addressing feedback from:

- missing function reference
https://github.com/vercel/next.js/issues/77190
- Error boundaries: https://github.com/vercel/next.js/issues/42525
- RedirectType: https://github.com/vercel/next.js/issues/59160
- generateMetadata can be included into static builds:
https://github.com/vercel/next.js/issues/80499

Also the headings here,
https://nextjs.org/docs/app/guides/local-development are not properly
nested

---------

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
 2025-06-26 20:07:53 +02:00
Joseph 7678bb904e docs: link api reference pages/app router divergence (#80955) 
This PR https://github.com/vercel/next.js/pull/80922 highlighted an
issue with the Link API reference.

Looking further into it I saw that we had mixed a few `AppOnly` +
`PagesOnly` tags, and needed a few more changes.
 2025-06-26 19:01:50 +02:00
Joseph b3e6b5b6e6 Docs/fetching data deduping (#80806) 
Fixes: https://github.com/vercel/next.js/issues/77077
https://github.com/vercel/next.js/issues/80790

- We are missing the deduping step that wraps with React.cache
- Add some more clarify about passing cache, current and future renders

Closes: https://linear.app/vercel/issue/DOC-4806/fetching-dedupe

---------

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
 2025-06-26 16:41:42 +02:00
Joseph 74b7cc339a docs: Add a link to what opts into dynamic rendering (#80910) 
Fixes:
https://github.com/vercel/next.js/issues/66871#issuecomment-3005875361

Let's add this patch quickly. I take over the Devin PR - and try to get
it merged in the coming days.
 2025-06-26 16:32:02 +02:00
Joseph 28e072705d docs: Use phosphor icons import perf optimization (#80811) 
Fixes: https://github.com/vercel/next.js/issues/80800

`react-icons` only supports the pattern we show through
`react-icons/all-files`, which hasn't been updated in the past 5 years.
`react-icons` does group icons by sets, so the recommendation about
sticking to a set is still valid.

I chose `@phosphor-icons/react`, since they also have a section on why
importing only the icon you need is a good idea.
 2025-06-26 15:27:31 +01:00
Ben Gubler 8b8057d307 docs: add explanation of --disable-git command (#80882) 
The `--disable-git` command was implemented in #68821 (released in
`v15.0.0-canary.119`).

It was documented in create-next-app/README.md, but not in the website.
I've seen several discussions online about the feature (usually from
people who remember an old `--no-git` flag) so this will be nice to
publish.

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-06-25 18:46:53 +02:00
JJ Kasper d88e313cf7 Add htmlrewriter to default server externals (#80819) 
This package needs to be externalized to have it's wasm dependencies
traced properly for node runtime so this adds it to our default list.

x-ref: [slack
thread](https://vercel.slack.com/archives/C07LQPFERGF/p1750713377659779?thread_ts=1750693981.162239&cid=C07LQPFERGF)
 2025-06-23 21:57:34 +00:00
Joseph 5e5a623cb5 chore: Dynamic error does not change dynamicParams (#80796) 
Closes:
https://linear.app/vercel/issue/DOC-4725/docs-dynamic-dynamicparams
Fixes: https://github.com/vercel/next.js/issues/80749
 2025-06-23 07:50:55 -05:00
Magnus d5410c26a5 docs: add csp and content disposition type (#80735) 
Add `contentSecurityPolicy` to Image Component in docs. Also follow up
in on the type in `image-config.ts` to use the updated docs.

---------

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
 2025-06-20 18:06:55 -04:00
Nemanja Kostadinovic 693619fddb Docs: Update code snippets in linking and navigating guide (#80652) 
This PR updates code snippets in linking and navigating guide in docs.
It also replaces wrong file name in one of the snippets.
 2025-06-18 11:42:42 +00:00
Hendrik Liebau 36c4dd475d Docs: Remove reference to deleted experimental turbotrace feature (#80572) 
The experimental `turbotrace` feature was removed in #71359, and hasn't
been available since Next.js v15.0.3.
 2025-06-18 09:27:28 +02:00
Joseph 4fa1c16809 docs: streaming metadata, dynamic pages and generateMetadata (#80453) 
Closes:
https://linear.app/vercel/issue/DOC-4687/docs-streaming-metadata-implications

---------

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
 2025-06-17 10:45:56 +02:00
dan 7dedc5b19f Explain how to use searchParams prop (#80579) 
I think this is a glaring omission from the docs that makes it very
difficult to understand how to use these API right.

See [this discussion on
Reddit](https://www.reddit.com/r/reactjs/comments/1lar2ss/comment/my2e3kl/).

I took a minimal approach but really this should be properly explained
somewhere because nobody knows this prop exists.
 2025-06-16 22:27:40 +02:00
Delba de Oliveira 2e2ee08b60 Docs IA 2.0: Delete routing section, add BFF guide, polish getting started (#80365) 
Closes:
https://linear.app/vercel/issue/DOC-4686/clean-up-routing-section
Redirects: https://github.com/vercel/front/pull/47151

---------

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
 2025-06-16 13:42:20 +01:00
Sajad Torkamani 27fed1c1b6 docs: fix typo (#80501) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-06-16 11:47:46 +00:00
Sajad Torkamani 1e5bb42a81 docs: fix typo (#80500) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-06-16 11:46:52 +00:00
Sajad Torkamani 029c8638f7 docs: fix typos (#80503) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-06-16 11:44:53 +00:00
루밀LuMir 4d133b0aeb docs: fix a typo in static-exports.mdx (#80541) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Hello, I’ve fixed a typo from `an` to `a`.

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-06-16 11:39:12 +00:00
Bob Ziroll dcdb2e18d6 Fix small grammar error in searchParams section (#80548) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: JJ Kasper <jj@jjsweb.site>
 2025-06-16 11:38:21 +00:00
Sajad Torkamani 3efa94ec5b docs: fix typo (#80549) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
 2025-06-16 11:33:58 +00:00
Sherri Cui 3d599a673b Fix variable assignment in docs example (#80418) 
### What?
Fixes small bug in Javascript code example where same variable is
declared again.

### How?
Same as this PR #74744 which fixed the Typescript code.

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
 2025-06-13 12:22:26 +00:00
Mauro Bonfietti e1045df08d Update from-create-react-app.mdx (#80451) 
<!-- 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(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com>
 2025-06-13 12:11:26 +00:00
Joseph f646f4df2f chore: Remove useActionState from auto wrapping list (#80420) 
Fixes: https://github.com/vercel/next.js/issues/80419
 2025-06-12 11:41:26 +01:00
Delba de Oliveira 2b76ed70bc Docs: Polish Getting Started section (#80402) 
Please merge this PR first: https://github.com/vercel/next.js/pull/80401

- Reorder pages. Group routing + rendering + data fetching, and UI
concerns (styling, css, images, etc)
- Update page titles to use keyword instead of "How to" for search
results

---------

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
 2025-06-11 14:02:43 +00:00
Joseph 2251d0f74a docs: server-only/client-only in Next.js (#80408) 
Closes:
https://linear.app/vercel/issue/DOC-4679/server-only-client-only-as-managed-by-nextjs
Fixes: https://github.com/vercel/next.js/issues/71071
 2025-06-11 14:06:46 +02:00
Delba de Oliveira 22ca7677bb Docs: Getting Started feedback (#80401) 
Closes:

- https://github.com/vercel/next.js/issues/76573
- https://github.com/vercel/feedback/issues/97181
- https://github.com/vercel/feedback/issues/96268
- https://github.com/vercel/feedback/issues/95318
- https://github.com/vercel/feedback/issues/95317
- https://github.com/vercel/feedback/issues/93861
- https://github.com/vercel/feedback/issues/91802
- https://github.com/vercel/feedback/issues/97192

---------

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
 2025-06-11 12:42:31 +01:00
Delba de Oliveira 7114fd23a5 Docs: Clarify how intercepting routes work and update example (#80145) 
Closes: https://github.com/vercel/next.js/issues/78255

---------

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-06-11 07:34:10 +01:00
Joseph f63088d2d1 docs: Middleware fetching is not cached (#80378) 
Closes:
https://linear.app/vercel/issue/DOC-4751/docs-missing-middleware-caching-information-also-ts-types-issue
Fixes: https://github.com/vercel/next.js/issues/77900

Note that the TypeScript (should the TS plugin detect fetch
`options.next` used in middleware and error out?) issue is still
pending. It will be eventually handled.
 2025-06-10 19:58:20 +02:00
Joseph 9497952629 Docs: broken links in caching (#80369) 
Fixes a couple of broken links in caching.
 2025-06-10 16:49:11 +01:00
Delba de Oliveira 1f3a186a8d Docs: Add prefetching guide (#80152) 
To do: 
- [x] Triggering unwanted side-effects during prefetching -
@delbaoliveira
- [x] Preventing too many prefetches - @delbaoliveira 
- [x] Disabling prefetching on hover - @icyJoseph 
- [x] Ejected link - soft navigation with `onClick` and `router.push` -
@icyJoseph

---------

Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
Co-authored-by: Lee Robinson <lee@leerob.com>
 2025-06-10 08:21:27 -05:00
Delba de Oliveira bbaa164737 Docs IA 2.0: Move examples to middleware.js API reference (#80363) 
Part of:
https://linear.app/vercel/issue/DOC-4686/clean-up-routing-section
 2025-06-10 08:00:17 -05:00
Delba de Oliveira 39fbaaf46b Docs IA 2.0: Move examples to route.js API reference (#80360) 
Part of:
https://linear.app/vercel/issue/DOC-4686/clean-up-routing-section

---------

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
 2025-06-10 07:02:33 -05:00
Delba de Oliveira 24434f18db Docs: Add Data Security Guide (#80249) 
Closes: https://linear.app/vercel/issue/DOC-4678/guide-data-security

Please merge this PR first: https://github.com/vercel/next.js/pull/80242

---------

Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
Co-authored-by: Joseph <joseph.chamochumbi@vercel.com>
 2025-06-10 06:52:38 -05:00
Joseph e74a824577 docs: Incremental cache is not used for cache-control: no-cache requests (#80352) 
Closes: #80346

-
https://github.com/vercel/next.js/blob/2f63e47d739dd9f70c93c68f2d3b6a582595c498/packages/next/src/server/lib/patch-fetch.ts#L807-L812
-
https://github.com/vercel/next.js/blob/2f63e47d739dd9f70c93c68f2d3b6a582595c498/packages/next/src/server/lib/incremental-cache/index.ts#L417-L426
 2025-06-10 11:52:07 +02:00
Joseph 0272c7f763 Docs: Add rspack community collab (#80217) 
Closes:
https://linear.app/vercel/issue/DOC-4747/a-simple-rspack-reference

---------

Co-authored-by: Rich Haines <hello@richardhaines.dev>
 2025-06-09 08:42:25 +00:00