Commit Graph
592 Commits
Author SHA1 Message Date
StevenandGitHub c010ecb237 Revert "docs: revert image 15.3 change until live" (#77977)
Reverts vercel/next.js#77941
2025-04-09 08:32:36 -07:00
Jiwon ChoiandGitHub b9620e6b1f docs: improve file tree (#77889)
The file tree can be improved and share the same convention:

- Use the `txt` file extension.
- One tab indented.
- Use file tree with root `.` and trailing slash for folders.

x-ref: https://tree.nathanfriend.io
2025-04-09 12:53:44 +02:00
Lee RobinsonandGitHub 27bb7066dc docs: revert image 15.3 change until live (#77941) 2025-04-08 12:54:25 -05:00
StevenandGitHub c9e238edf9 feat(next/image): support new URL() for images.remotePatterns (#77692)
Configuring `remotePatterns` can be a hassle because you have to define
each of the parts. And if you forget a part, its a wildcard meaning it
will match anything. This is usually not desirable since most remote
images don't allow query strings.

This PR adds support for using an array of `URL` objects when defining
`images.remotePatterns`.

```js
module.exports = {
  images: {
    remotePatterns: [
      new URL('https://res.cloudinary.com/my-account/**'),
      new URL('https://s3.my-account.*.amazonaws.com/**'),
    ],
  },
}
```

Note that wildcards must be explicit and anything missing is assumed to
no longer match.
2025-04-02 19:13:57 -04:00
Sam KoandGitHub 8dd0b56fb6 docs(errors): update suppressHydrationWarning section (#76521)
## Why?

We should clarify that React will **not** attempt to patch mismatched text content when using `suppressHydrationWarning`.

- Related: https://github.com/reactjs/react.dev/pull/7651
- x-ref: https://github.com/vercel/next.js/discussions/75890
2025-02-26 12:11:59 -08:00
Sam KoandGitHub d55c00d842 docs(errors): minor update to failed-to-find-server-action error page (#76296)
## Why?

Follow up to https://github.com/vercel/next.js/pull/75678#discussion_r1964355401.
2025-02-20 13:57:36 -08:00
Sam KoandGitHub beb1f72e6d docs(errors): add failed-to-find-server-action error page (#75678)
## Why?

We should also have an error page when somebody gets this error → https://github.com/vercel/next.js/blob/d70cac3eb4dee1d1361629d1b4c765365f184e26/packages/next/src/server/app-render/action-handler.ts#L1086.
2025-02-20 12:31:59 -08:00
Maxim EvtushandGitHub 173a461ef7 fix: typos in documentation files (#75816) 2025-02-11 21:04:37 -06:00
JJ KasperandGitHub 2e114e44c5 Fix linting between lint-check and lint-staged (#74503) 2025-01-03 23:17:14 +00:00
StevenandGitHub d70595e5b6 feat(next/image): add support for images.qualities in next.config (#74257)
This PR adds support for `images.qualities` configuration which is an
allowlist of qualities that can be used with the quality prop on the
Image component.

- Depends on https://github.com/vercel/vercel/pull/12792
2025-01-03 20:43:29 +00:00
StevenandGitHub 2a25cbdd99 chore(docs): add missing search: '' on remotePatterns (#73925)
We typically add `search: ''` on `remotePatterns` to disallow the query
string, which is the most common case.

There were a few missing places in the docs so this PR fills in those
gaps.
2024-12-13 17:05:47 -05:00
26e8b765ae Docs clean up: Merge and delete content from routing/index.mdx (#73859)
Please merge this PR first: https://github.com/vercel/next.js/pull/73858

Closes: https://linear.app/vercel/issue/DOC-4049/delete-routingindexmdx

The content for this page has already been moved to the `Getting
Started` section or `API Reference`.

---------

Co-authored-by: Rich Haines <[email protected]>
2024-12-13 13:16:26 +00:00
Hendrik LiebauandGitHub 7db3bf73cb Fix unstable_allowDynamic when used with pnpm (#73732)
When using dependencies in Middleware that make use of dynamic code evaluation, Next.js emits a build error because this is not supported in the Edge runtime.

In rare cases, when the code can not be reached at runtime and can't be removed by tree-shaking, users might opt in to using the `unstable_allowDynamic` config.

When combined with pnpm, the provided glob patterns as documented at https://nextjs.org/docs/messages/edge-dynamic-code-evaluation#possible-ways-to-fix-it did not match correctly because of pnpm's use of the `.pnpm` directory.

To fix the pattern matching, we need to provide the `dot` option to [picomatch](https://github.com/micromatch/picomatch), which enables dotfile matching.

_Side note: Ideally we would detect dynamic code evaluation after tree shaking, to reduce the number of cases where users need to revert to using `unstable_allowDynamic`._

fixes #51401
2024-12-10 22:14:40 +01:00
13880d37d2 docs(typo): fix typos in file conventions, functions, and errors (#73376)
`occured` -> `occurred`
`compatability` -> `compatibility`

Co-authored-by: Delba de Oliveira <[email protected]>
2024-12-03 14:01:38 +00:00
LioRaelandGitHub f8fddfa1dd docs: add await before headers() and cookies() calls (#73315) 2024-11-28 15:19:47 +01:00
2a4bdbd4ab docs: fix code block language (#72839)
## Summary
Change `jsx` to `diff` in
[next-dynamic-api-wrong-context](https://github.com/vercel/next.js/blob/canary/errors/next-dynamic-api-wrong-context.mdx)
error page.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-19 09:58:44 +00:00
6f4352993d docs: add and unify notes to error pages (#72838)
## Description
Unify the note format according to the [contribution
guide](https://nextjs.org/docs/community/contribution-guide#notes).
In addition, add missing bullet points to useful links.

### Improving Documentation

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

---------

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-19 09:44:42 +00:00
f5ead56cb4 docs: add the section titles to error page (#72942)
## Summary
Add the paragraph name to
[next-prerender-crypto](https://github.com/vercel/next.js/blob/canary/errors/next-prerender-crypto.mdx)
error page like [other next-prerender
pages](https://github.com/vercel/next.js/blob/canary/errors/next-prerender-current-time.mdx).

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-19 09:00:36 +00:00
e5ce54de0b docs: use relative urls (#72941)
## Description
Follow up #52038.
Remove `https://nextjs.org` from URL in [error
pages](https://github.com/vercel/next.js/tree/canary/errors).

### Improving Documentation

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

---------

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-19 08:58:29 +00:00
016b033aaa Fix broken link to the rootDir doc (#72893)
### What?

Fix broken link to the `rootDir` doc at
https://nextjs.org/docs/messages/no-html-link-for-pages#options

### Why?
This is because there is an extra space between a path and an anchor. 

### How?

This PR removes it to fix the format.

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-19 08:50:01 +00:00
20dc57391e docs: fix code block language in error pages (#72943)
## Summary
Update code block language in [error
pages](https://github.com/vercel/next.js/tree/canary/errors).

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-19 07:56:55 +00:00
Jiwon ChoiandGitHub c469404824 improve no-img-element lint error message (#72410)
### Why?

To customize Image Optimation, the user can use a custom loader, but
that information was out from the related lint error message.

Closes NDX-181
2024-11-12 21:48:12 +09:00
691eeae8fb docs: unify the header deps by removing # (#72451)
## Description
Follow up #72391.
I missed some error pages.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-08 11:20:34 -08:00
Delba de OliveiraandGitHub 0b35ddd825 Docs: Move next.config.js API pages under a config folder, fix headings in TS and ESLint config pages (#72465)
This PR:

- Moves `next.config.js` options under a "config" folder which includes
references for other configuration such as the ESLint plugin. I figure
it would be tidier than having "Next.config.js Options" and "Config" in
the API reference.
- Fixes the issue with the "config" folder not showing up in canary:
https://linear.app/vercel/issue/DOC-3749/bug-figure-out-why-new-config-folder-isnt-showing-up-in-the-canary
- Fixes the indentation issues and missing example header (caused by an
invisible character).

Redirects: https://github.com/vercel/front/pull/38704
2024-11-08 14:48:55 +00:00
74a19b7467 docs: unify the header deps by removing # (#72391)
## Summary
Remove redundant `#` from [error
pages](https://github.com/vercel/next.js/tree/canary/errors).

## Description
Follow up #52038 and #72263.
Updated
[template.txt](https://github.com/vercel/next.js/blob/canary/errors/template.txt)
and clarified the header deps.
Then rewrite as per the template.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-07 08:58:43 +00:00
fbb3a766e7 Update Cloudflare Auto Minify link due to feature deprecation (#72417)
This PR updates the link for the Cloudflare Auto Minify feature, as it
has been deprecated. Cloudflare now recommends disabling this feature to
avoid potential issues. The link and related references have been
modified to reflect this update and ensure accurate information for
users.

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-07 08:52:56 +00:00
fa8d558154 Docs: Split Getting Started between App and Pages, improve Installation page (#72178)
Prepare **Getting Started** Section for upcoming changes, and work on
the first page: `Installation`.

Closes: 
-
https://linear.app/vercel/issue/DOC-3703/update-how-getting-started-is-handled-in-next-site
-
https://linear.app/vercel/issue/DOC-3694/page-how-to-set-up-a-new-nextjs-project-installation
- https://linear.app/vercel/issue/DOC-3707/create-subsection-for-plugins
- https://linear.app/vercel/issue/DOC-3709/eslint-plugin-api-reference
- https://linear.app/vercel/issue/DOC-3710/typescript-reference-page

### Key Changes: 

- Duplicate Getting Started Section between App and Pages Router docs 
- Since getting started will vary between the routers, each docs needs
to have their own Getting Started section
- Reorganize folder numbers
   
**Installation Page**: 
- Split app and pages router specific information
- Rename "Installation" to "How to set up a Next.js application" for SEO
- Add setup instructions for **TypeScript**
- Add setup instructions for **ESLint**
- Add setup instructions for **Absolute Imports and Module Path
Aliases**

**Side effects from moving content around**:
- Create a subsection in API Reference called **Configuration**. 
   - Add ESLint Plugin page, and update it to follow template
   - Add TypeScript page, and update it to follow template
- Remove the **Absolute Imports and Module Path Aliases** page, it's
small enough to live under the set up instructions.

---------

Co-authored-by: Rich Haines <[email protected]>
2024-11-06 12:32:05 +00:00
Delba de OliveiraandGitHub 8f99ab20ae Docs: Remove legacy tags from unstable_cache and unstable_noStore (#72134)
This was a premature move as the docs made their way into the stable
version. Can't risk these being merged just yet, and they're also not in
canary.
2024-11-06 08:35:52 +00:00
974767e42d Fix code examples in error page (#72259)
This PR fixes the code examples in the Next prerender missing suspense
error page

<!-- 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 <[email protected]>
2024-11-06 08:16:56 +00:00
ed239c40b5 docs: update error template.txt (#72263)
## Summary
Update [error
template.txt](https://github.com/vercel/next.js/blob/canary/errors/template.txt)
following #52038 changes.

## Description
1. Remove errorId header
2. Section header is double sharp `##` instead of four sharp `####`

### Adding or Updating Examples

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-06 08:16:40 +00:00
2d549683a6 docs: change runtime value in example code (#72274)
## Description
[Invalid Page / API Route
Config](https://nextjs.org/docs/messages/invalid-page-config) shows some
examples.
However, runtime examples are same `nodejs` runtime.
Then I add `edge` value instead of duplicate value.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-06 08:16:38 +00:00
f8b4b227e1 docs: add filename to code block (#72275)
## Summary
[Use Code Block
filename](https://nextjs.org/docs/canary/community/contribution-guide#language-and-filename)
instead of comment.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-06 08:07:02 +00:00
aabb04c983 docs: remove -/+ diff marker (#72278)
## Description
[next-request-in-use-cache error
page](https://nextjs.org/docs/messages/next-request-in-use-cache) uses
-/+ icons in code block.
However, it doesn't work correctly because it's not diff code block.
Then add highlight instead of that.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-05 07:33:40 +00:00
7b2acfc701 docs: replace let with const (#72279)
## Description
Replace `let` with `const` in [No async client component error
page](https://nextjs.org/docs/messages/no-async-client-component)
example.
Since in these examples, it doesn't need to be a `let`, as it doesn't do
any reassignment.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-05 07:28:37 +00:00
e5e1cfe4c8 docs: add bash filename=Terminal to code block (#72281)
## Summary
Add `bash filename="Terminal"` to improve readability.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-05 07:28:23 +00:00
bca3b9e3cd docs: add missing Useful Links to error pages (#72282)
## Summary
Add missing `## Useful Links` section header to adapt
[template](https://github.com/vercel/next.js/blob/canary/errors/template.txt).

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-11-05 07:20:03 +00:00
7fe9065917 docs: typo file extension (#72272)
## Summary
Change [language and
filename](https://nextjs.org/docs/canary/community/contribution-guide#language-and-filename)
for match code block language.

### Improving Documentation

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

Co-authored-by: JJ Kasper <[email protected]>
2024-11-04 23:16:21 +00:00
926752ecfe docs: add missing before section name (#72277)
## Summary
Only exist `after` directive at [next-prerender-current-time error
page](https://nextjs.org/docs/messages/next-prerender-current-time).
Then add `before` section name.

### Improving Documentation

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

Co-authored-by: JJ Kasper <[email protected]>
2024-11-04 23:06:27 +00:00
Delba de OliveiraandGitHub 9bbf1d023c Docs: Fix css modules page in Pages docs (#72135)
Re: https://vercel.slack.com/archives/C07BS1WEYAZ/p1730162050697879
2024-11-04 12:23:43 +00:00
b5531e99e5 docs: add missing root directory / to path (#72118)
## Summary
Add a slash to correct the problem.

### Improving Documentation

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

Co-authored-by: Delba de Oliveira <[email protected]>
2024-10-31 14:06:53 +00:00
2139a141cb fix typo in doc (#71600)
<!-- 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 #

-->
The fix in https://github.com/vercel/next.js/pull/70680 is still
misleading. `missingSuspenseWithCSRBailout` is valid in `14` and invalid
in `Above 14`.

Co-authored-by: JJ Kasper <[email protected]>
2024-10-30 18:57:36 +00:00
5d972b5986 docs: fix incorrect link in url-deprecated.mdx (#71787)
## Summary
Delete an incorrect link and update a right link.

### Improving Documentation

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

---------

Co-authored-by: JJ Kasper <[email protected]>
2024-10-29 23:54:28 +00:00
5ea36c50c6 docs: rename md to mdx in errors directory (#71785)
## Description
Some files use `md` extension.
So, I corrected it by changing the extension to `mdx`.

### Improving Documentation

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

Co-authored-by: JJ Kasper <[email protected]>
2024-10-29 12:01:59 -07:00
7308aa8a23 docs: fix URL for error message (#71788)
## Description
Fix URL for https://nextjs.org/docs/messages/missing-root-layout-tags

❌wrong:
https://nextjs.org/docs/app/building-your-application/routing/pages-and-layouts#root-layout-required
✅correct:
https://nextjs.org/docs/app/building-your-application/routing/layouts-and-templates#root-layout-required

### Improving Documentation

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

Co-authored-by: JJ Kasper <[email protected]>
2024-10-29 18:59:10 +00:00
fddd022e1b docs: fix broken link of new comments path (#71674)
# Summary
Add missing comments path to which #61416 changed.

### Improving Documentation

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

Co-authored-by: JJ Kasper <[email protected]>
2024-10-29 11:54:28 -07:00
Antonis AngelisandGitHub 9d8b145dfc Update sync-dynamic-apis.mdx (#71907) 2024-10-26 22:50:01 +02:00
IsmaelandGitHub ae282ae540 Next docs broken links (#71823) 2024-10-24 12:55:01 -07:00
Jiwon ChoiandGitHub ffde232be2 docs: remove "use cache" on before code snippet (#71815)
Removed `"use cache"` directive on the before example of the code
snippet.
2024-10-24 10:57:19 -07:00
Josh StoryandGitHub 17f4291318 [dynamicIO] refine error message and docs (#71781)
refines the error message for non-prerenderable holes while prerendering
as well as the docs
2024-10-24 00:31:29 -07:00
Zack TannerandGitHub 1cb70c485c docs lint (#71748)
`easy` and `just` are failing lint checks.
2024-10-23 19:23:08 +00:00