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
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
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
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
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
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
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
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
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
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
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
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
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
9497952629
Docs: broken links in caching ( #80369 )
...
Fixes a couple of broken links in caching.
2025-06-10 16:49:11 +01:00
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
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
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
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
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
f05106dad5
fix typo ( #80282 )
...
<!-- 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 #
-->
Fix typo
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-06-07 23:28:44 +00:00
4b5db16725
Turbopack Build: docs for unsupported composes handling ( #80238 )
...
## What?
Adds additional documentation about `.css` (not `.module.css`) files
being imported from a `.module.css` (CSS Module) using `composes` or
`@import` and updates the tests to reflect the specific case not being
supported.
2025-06-06 12:39:49 +02:00
083b924c01
Docs: Linking and Navigating Page ( #80103 )
...
Closes:
https://linear.app/vercel/issue/DOC-4718/linking-and-navigating-page
This PR:
- Adds a linking and navigating page to getting started:
- Introduces how navigation works and the built-in Next.js optimizations
(prefetching, client-side transitions, etc)
- Discusses what can cause slow transitions and how to optimize it.
- Updates the loading.js API reference
Redirects:
- https://github.com/vercel/front/pull/46788
---------
Co-authored-by: Joseph <joseph.chamochumbi@vercel.com >
2025-06-06 10:37:16 +01:00
56c3dce5a8
docs: add Docker development performance guidance for Mac/Windows ( #80002 )
...
# Add Docker Development Performance Documentation
This PR adds documentation about Docker performance issues during
development on Mac and Windows, based on community feedback.
## Changes
- Added section 8 to the local development performance guide explaining
Docker filesystem performance issues
- Added a development note to the Docker deployment section recommending
local development for better performance
- Provides clear guidance on when to use Docker vs local development
## Context
Based on community discussion about slow HMR when using Docker for
development on Mac/Windows compared to local development. Docker's
filesystem access on these platforms can cause significant performance
degradation.
Link to Devin run:
https://app.devin.ai/sessions/7feff3a0c28c4f9ab41014fec498e00e
Requested by: lee@vercel.com
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: lee@vercel.com <lee@vercel.com >
Co-authored-by: Lee Robinson <lee@leerob.com >
2025-06-05 11:57:43 -05:00
e2ba7905bd
small typo fix ( #80171 )
...
`metadat` -> `metadata`
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-06-05 06:41:25 +00:00
4a16e4341b
Docs: preload entries impact on memory consumption ( #80098 )
...
Closes:
https://linear.app/vercel/issue/DOC-4736/docs-experimentalpreloadentriesonstart
x-ref: https://github.com/vercel/next.js/issues/77318
---------
Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com >
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-06-04 13:42:46 +00:00
750eae084a
Docs: Improve Turbopack webpack loader documentation ( #79523 )
...
# Improve Turbopack webpack loader documentation
## Description
This PR improves the Turbopack webpack loader documentation by:
1. Clarifying that the list of supported loaders is not exhaustive
2. Adding a more detailed example showing how to pass options to loaders
using the object format
3. Adding graphql-tag/loader to the list of supported loaders based on
customer feedback
This addresses customer confusion about how to pass options to loaders
and clarifies that many loaders beyond those explicitly listed will
work.
Link to Devin run:
https://app.devin.ai/sessions/33095930f1f34a6daf81c2ce7eca3be0
Requested by: lee@vercel.com
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: lee@vercel.com <lee@vercel.com >
Co-authored-by: Tim Neutkens <tim@timneutkens.nl >
2025-06-03 19:00:31 +02:00
ebcec54e03
docs: Manual calls to action should we wrapped in startTransition ( #80101 )
...
Fixes : #78063
As noted, not wrapping in `startTransition`, doesn't really work as
expected, for example `isPending` is not updated at all.
2025-06-03 14:13:55 +02:00
7a57ca7b61
chore: Use same function references in useReportWebVitals examples ( #79963 )
...
Closes: https://linear.app/vercel/issue/DOC-4726/docs-usereportwebvitals
FIxes : #79940
---------
Co-authored-by: Lee Robinson <lee@leerob.com >
2025-06-02 14:00:45 +00:00
e2173f1360
docs: Drop innacurate override information for dynamicParams ( #79966 )
...
Closes:
https://linear.app/vercel/issue/DOC-4725/docs-dynamic-dynamicparams
As far as I have been able to gather, `dynamicParams` always defaults to
`true`.
2025-06-02 08:57:04 -05:00
9748d9da17
docs: Reference to statically imported images ( #80048 )
...
Closes:
https://linear.app/vercel/issue/DOC-4730/docs-nextimage-local-images-broken-snippet
Fixes : #80023
Made the static image imports, into a sub section of local images, and
referenced how their width/height is auto calculated.
-
https://github.com/vercel/next.js/blob/fde4f7f2974d5870a74c196383af70df981de39e/packages/next/src/shared/lib/get-img-props.ts#L397-L398
here we copy the dimensions for statically imported images
There's also some tests that reference this usage:
-
https://github.com/vercel/next.js/blob/00c52d1506638ed8a4e46ac97ad999454c4823d1/test/integration/next-image-new/base-path/pages/static-img.js#L23
---------
Co-authored-by: Lee Robinson <lee@leerob.com >
2025-06-02 13:56:39 +00:00
b5b2a6c14b
Fix incorrect route param ( #79795 )
...
In the example under the "Generated Metadata" section of the page, the
route is defined as `/app/blog/[slug]/page.tsx`, but the Props type uses
`id` instead of `slug`. This fixes the mismatch to reflect the actual
dynamic route segment
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-05-30 11:02:41 +00:00
323ec0aea7
docs: fix incorrect usage of Promise in page params example ( #79804 )
...
The documentation incorrectly used `params: Promise<{ slug: string }>`
in an example and attempted to use `await` in a non-async function.
This commit updates the example to reflect the correct usage:
- `params` should be a synchronous object: `{ slug: string }`
- The page component should be declared `async` if using `await` inside
This fixes a misleading example and aligns it with actual behavior in
the Next.js App Router: [cause]: SyntaxError: await is only valid in
async functions and the top level bodies of modules
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-05-30 11:01:49 +00:00
df846a296b
docs: force-static w/ revalidate, revalidatePath, and revalidateTag ( #79780 )
...
Closes:
https://linear.app/vercel/issue/DOC-4713/force-static-w-revalidatetagrevalidatepathrevalidate
2025-05-28 11:24:12 -05:00
e66680dcf9
Docs: Fix headings ( #79777 )
2025-05-28 11:31:06 +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
fc17ba9710
Docs: scrub html in ld+json script ( #79627 )
...
Closes:
https://linear.app/vercel/issue/DOC-4708/json-ld-security-w-jsonstringify
Fixes: https://github.com/vercel/next.js/issues/79593
2025-05-27 15:23:05 +02: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
63ed70ba41
Docs IA 2.0: Move Redirects page to guides ( #79447 )
...
Closes: https://linear.app/vercel/issue/DOC-4695/guide-redirects
Redirects: https://github.com/vercel/front/pull/46041
2025-05-27 12:20:11 +01:00
37ee4452b8
Next IA 2.0: Create Route Groups API reference, simplifying wording ( #79444 )
...
Closes:
https://linear.app/vercel/issue/DOC-4676/dynamic-route-segments-api-reference
Redirects: https://github.com/vercel/front/pull/46032
---------
Co-authored-by: Ismael <ismael@vercel.com >
2025-05-27 10:31:44 +00:00
2d81adc520
Docs IA 2.0: Create Dynamic Segments API reference, add example to getting started. ( #79439 )
...
Closes:
https://linear.app/vercel/issue/DOC-4676/dynamic-route-segments-api-reference
Redirects: https://github.com/vercel/next.js/pull/79439
2025-05-27 10:51:59 +01:00
f87fee7b28
Docs IA 2.0: Update template.js API reference ( #79490 )
...
Merge template.js information from BYA and update API reference to
follow the convention.
Please merge this PR first: https://github.com/vercel/next.js/pull/79453
Closes:
https://linear.app/vercel/issue/DOC-4696/routing-section-layouts-and-templates
2025-05-27 10:30:17 +01:00
f18b756cde
Docs IA 2.0: Add examples to layout.js ( #79453 )
...
In the **layout.js** API reference, we talk about the limitations of
layouts but don't provide alternative examples. This simplifies the
wording, and adds examples using the recommended APIs.
Also adds more general `layout.js` examples.
Part of:
https://linear.app/vercel/issue/DOC-4696/routing-section-layouts-and-templates
Follow up: Look into template.js
---------
Co-authored-by: Joseph <joseph.chamochumbi@vercel.com >
2025-05-27 10:02:17 +01:00
d9e41e43d0
Docs IA 2.0: Create intercepting and parallel routes API reference ( #79405 )
...
Parallel and intercepting routes are more "side-quests" than main
features, so they are not included in the Getting Started. We did not
have an API reference for them, so they have been moved under
File-system conventions (which was renamed to account for folder
conventions).
Closes:
-
https://linear.app/vercel/issue/DOC-4683/api-reference-intercepting-routes
- https://linear.app/vercel/issue/DOC-4684/api-reference-parallel-routes
Redirects:
- https://github.com/vercel/front/pull/45973
2025-05-27 09:51:43 +01:00
b89caa422a
Docs IA 2.0: Create Forms guide ( #79288 )
...
Closes: https://linear.app/vercel/issue/DOC-4671/forms
No redirects needed yet as no pages were deleted.
2025-05-27 08:34:38 +00:00
b3e6064cc3
docs (data fetching): fix typo in startTransition call ( #79578 )
...
Fix typo in useEffect hook when calling the startTransition hook.
<!-- 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-05-24 20:37:47 +00:00
bb3284b2d9
docs: Rename CSS snippet to blog.module.css ( #79507 )
...
Closes: https://linear.app/vercel/issue/DOC-4702/getting-started-css
2025-05-23 10:08:15 +02:00
129ab0ee16
Docs: Align with react docs server functions ( #79442 )
...
Closes:
https://linear.app/vercel/issue/DOC-4070/review-mentions-of-server-actions-to-server-functions
---------
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2025-05-22 12:38:05 +02:00
6020a8b1c0
Docs IA 2.0: Reorder PPR page and fix some nits ( #79282 )
...
Co-authored-by: Joseph <joseph.chamochumbi@vercel.com >
2025-05-22 06:15:27 +00:00
90b6f19b5d
Docs: Remove non breaking space ( #79468 )
...
For some reason a non breaking space, ASCII 160 had been used instead of
a regular space.
2025-05-21 20:35:04 +02:00
ed09804153
Docs: Fix broken link ( #79456 )
2025-05-21 09:48:37 -05:00
Sajad Torkamani