Commit Graph
5 Commits
Author SHA1 Message Date
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
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
IsmaelandGitHub ae282ae540 Next docs broken links (#71823) 2024-10-24 12:55:01 -07:00
445cc62b3e docs: update code block filename in dynamic API context error page (#67000)
The filenames of the two code blocks on this page
https://nextjs.org/docs/messages/next-dynamic-api-wrong-context are
written as comment instead of using the `filename` prop.


![image](https://github.com/vercel/next.js/assets/20135478/86b45742-cb83-4cd1-933c-a1c22f51e0fd)

---------

Signed-off-by: Eng Zer Jun <[email protected]>
Co-authored-by: Sam Ko <[email protected]>
2024-06-19 10:20:30 +00:00
Balázs OrbánandGitHub 971843d019 fix: clarify Dynamic API calls in wrong context (#62143)
### What?

An unactionable error is thrown when `headers()`, `cookies()` or other
Dynamic API functions are called outside the render/request context.
This PR clarifies what the user can do to fix the problem.

### Why?

The current error is  hard to understand

> Error: Invariant: `cookies` expects to have requestAsyncStorage, none
available.

### How?

I am adding a dedicated error page and rephrasing the error message.

Closes NEXT-2509
2024-02-19 13:41:14 +01:00