897d021d96
docs: csr-bailout debugging ( #86359 )
...
I think maybe these others need a hint too, let's get started with,
`errors/missing-suspense-with-csr-bailout` and `errors/prerender-error`
- errors/blocking-route.mdx
- errors/deopted-into-client-rendering.mdx
- errors/dynamic-server-error.mdx
- errors/next-prerender-crypto.mdx
- errors/next-prerender-current-time.mdx
- errors/next-prerender-sync-headers.mdx
- errors/next-prerender-sync-params.mdx
- errors/sync-dynamic-apis.mdx
2025-11-21 11:11:12 +01:00
fffb2eb6fb
Docs IA 2.0: Delete Error Handling page ( #79495 )
...
The content has already been migrated to
https://nextjs.org/docs/app/getting-started/error-handling .
Closes:
https://linear.app/vercel/issue/DOC-4700/bya-delete-error-handling-page
Redirects: https://github.com/vercel/front/pull/46127
2025-05-27 14:58:40 +00:00
8b7f937e36
Docs IA 2.0: Add Caching and Revalidating page ( #79493 )
...
Closes:
https://linear.app/vercel/issue/DOC-3700/getting-started-caching-and-revalidating-page
Redirects: https://github.com/vercel/front/pull/46120
2025-05-27 13:35:36 +01:00
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
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 <hello@richardhaines.dev >
2024-12-13 13:16:26 +00:00
7f41ea9111
docs: update prerender error ( #69744 )
...
Just adding more details here, as it was pretty bare before.
---------
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2024-09-13 18:17:51 +00:00
1710b3dc5d
Update prerender-error.mdx ( #68747 )
...
This is how I fixed the issue when this error message came up in my
command line.
<!-- 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: Lee Robinson <me@leerob.io >
2024-09-12 14:19:02 -07:00
83bd0f43e1
docs: improve prerender error message ( #64154 )
...
Based on customer feedback
---------
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2024-04-07 09:46:13 -05:00
22380dfe2a
Updates "Prerender Error" page for App Router ( #56044 )
...
I am open to alternative ideas on how to solve this.
Fixes https://github.com/vercel/feedback/issues/40502
2023-09-26 19:32:06 +00:00
44d1a1cb15
docs: Migrate error messages to MDX and App Router. ( #52038 )
...
This PR is part of a larger effort to migrate error messages to MDX and
use App Router: https://github.com/vercel/front/pull/23459
2023-07-05 06:11:16 -07:00
Joseph