720fe3577e
simplify vapid key generation docs ( #72916 )
...
<!-- 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 #
-->
### What?
Simplify Vapid key generation docs
### Why?
Creating a script is tedious.
The CLI can be used across projects without needing to reference and
recreate this script.
### How?
Added instructions to install `web-push` globally and how to run it.
---------
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2024-11-19 09:01:19 +00:00
172f3e3dd9
docs: update "Migrate to async Dynamic APIs" docs ( #72852 )
...
### What?
Update the example code with Codemods applied in [Migrate to async
Dynamic
APIs](https://nextjs.org/docs/app/building-your-application/upgrading/codemods#migrate-to-async-dynamic-apis )
docs
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2024-11-19 08:25:11 +00:00
0a7d97e660
docs: fix code block language in redirecting docs ( #72944 )
...
## Summary
Update incorrect code block languages at [redirecting
document](https://github.com/vercel/next.js/blob/canary/docs/01-app/02-building-your-application/01-routing/07-redirecting.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 <32464864+delbaoliveira@users.noreply.github.com >
2024-11-19 07:56:43 +00:00
a6c1005611
Clarify how MDX plugins are supported in Turbopack ( #72917 )
...
Followup to https://github.com/vercel/next.js/pull/72241 and
https://github.com/vercel/next.js/pull/72467
Documenting the new Turbopack support for MDX plugins (remark, rehype,
recma plugins):
- https://github.com/vercel/next.js/issues/71819#issuecomment-2482774351
<!-- 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 #
-->
### What?
Clarify that MDX-related plugins (remark and rehype plugins) are
supported when options are serializable, by using the new string name
config format
### Why?
Support was added in 72802
- https://github.com/vercel/next.js/pull/72802
### How?
Add a new section about using plugins with Turbopack
2024-11-18 15:40:17 +00:00
a2bd33f4e5
Add explicit section about type overriding for v15 ( #72866 )
...
This breaks out the type overriding note from a small good to know
section to it's own section as it's fairly important and easy to miss
currently. Also the minimal note isn't getting picked up in our search
currently.
x-ref: [slack
thread](https://vercel.slack.com/archives/C0676QZBWKS/p1731602395153929 )
2024-11-16 00:14:32 +01:00
f705f9a1a0
docs(data-fetching): fix static params as promise examples ( #72565 )
...
### Improving Documentation
- Since the params prop is now a promise, the type of params in the
generateMetadata and Page components has been changed from `{ id: string
}` to `Promise<{ id: string }>`.
---------
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2024-11-12 21:10:47 +00:00
23dbf29b08
docs(use-cache): add missing function to page component examples ( #72620 )
...
### Improving Documentation
- This PR updates Page component examples by adding `function` keyword
to ensure proper syntax highlighting 🙂
- Also includes the missing `export default` for page components, and
applies consistent code formatting.
<img width="675" alt="image"
src="https://github.com/user-attachments/assets/c081f866-8523-4597-aa56-7baad96eecb5 ">
<br />
2024-11-12 13:09:06 -08:00
b1f1328643
docs: remove unstable_after from Dynamic APIs ( #72595 )
...
This pull request removes the unstable_after from the Dynamic APIs, as
it does not cause a route to become dynamic.
2024-11-12 16:54:47 +00:00
f8a10c79bf
refactor(turbopack): Remove swc_css ( #72602 )
...
### What?
Remove `swc_css` from turbopack. It would not break the existing codebase, so it's fine.
2024-11-12 17:36:48 +09:00
0bc4086dff
Add expireTag and expirePath APIs ( #72485 )
...
This adds `expireTag()` and `expirePath` APIs which are replacing
`revalidateTag` and `revalidatePath`. As such this also marks
`revalidatePath` and `revalidateTag` as deprecated and marked for
removal.
The arguments passed to these methods match `revalidateTag` and
`revalidatePath` with the exception that `expireTag` can receive
multiple tags now as separate arguments which matches our new
`unstable_cacheTag()` API.
We are wanting to update these APIs as `revalidateTag` naming has caused
some confusion as to when the affected items will be updated. The
underlying behavior of `expireTag` is to mark an entry as out of date
and for it to no longer be used so we are expiring it.
If you call `expirePath('/blog/first'`) the next time that item is
requested it is considered expired so the cache will not be used for it
and a fresh entry will be generated. Similarly for `expireTag('posts',
'blog')` the next time any cache with that tag is requested it's
respective cache will not be leveraged and new cache will be populated.
---------
Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com >
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2024-11-11 19:23:39 +00:00
51ee1c7f59
Fix grammatical error: remove unnecessary 'a' in 03-server-actions-and-mutations.mdx ( #72496 )
...
#### Description:
- fix grammatical error: remove unnecessary 'a'
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2024-11-08 11:21:23 -08:00
d8732b9f71
fix: remove unnecessary fragment ( #72492 )
...
Hi, Team.
I'd like to contribute as removing unnecessary fragments.
I believe that the fragment will create one more grouping node on
virtual dom, which is not necessary on this example.
If it is essential, please kindly let me know why.
Thank you so much for your support.
### Improving Documentation
- remove unnecessary fragment tags
Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com >
2024-11-08 11:21:00 -08:00
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
302e0febf1
[Docs]: Remove try catch and link to error handling docs ( #72500 )
...
This PR updates the server actions error handling section to remove
advising using a try catch, in favor of linking to the Error Handling
docs, which has the correct information.
<!-- 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 #
-->
2024-11-08 14:16:56 +00:00
81271baece
Correct reason for Turbopack incompat, remove inaccurate "good to know" ( #72467 )
...
- https://github.com/vercel/next.js/pull/72241#discussion_r1832894901
<!-- 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 #
-->
### What?
1. Fix the incorrect statement added in #72241 , as per @timneutkens'
comment here:
- https://github.com/vercel/next.js/pull/72241#discussion_r1832894901
2. Remove the outdated "good to know" section stating that Turbopack
requires `mdxjs-rs` and is not compatible with `@next/mdx`
### Why?
The docs are currently incorrect
### How?
Edit [remark and rehype
plugins](https://nextjs.org/docs/app/building-your-application/configuring/mdx#remark-and-rehype-plugins )
section on docs page
---------
Co-authored-by: Tim Neutkens <tim@timneutkens.nl >
2024-11-07 17:59:00 +01:00
be40adb9d9
Add missing closing </AppOnly> ( #72453 )
...
The MDX was invalid after https://github.com/vercel/next.js/pull/72399
causing next-site deploy failures
(I'm not entirely sure if this is where the `</AppOnly>` should go, feel
free to correct that)
Closes PACK-3416
2024-11-07 11:40:25 +00:00
224447cd65
Getting Started Docs: Improve "Project Structure" page ( #72399 )
...
Closes:
- https://linear.app/vercel/issue/DOC-3695/page-project-structure
This PR:
- Splits the page between the app/pages and the router docs.
- Merge the colocation page from BYA.
2024-11-07 09:34:46 +00:00
856521bf47
docs(parallel-routes): update 11-parallel-routes.mdx example for modal closing ( #72210 )
...
docs(parallel-routes): update 11-parallel-routes.mdx example for modal
closing
- Updated `11-parallel-routes.mdx` to replace `'...'` with `null` in the
`page.tsx` return statement inside the slot for closing the modal when
navigating using `Link`.
- Also applied the same change in the `default.tsx` file to ensure
consistent behavior in the example.
<!-- 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 >
2024-11-07 09:11:34 +00:00
9d31638041
docs(route-handlers): add TS/JS switcher to Route Resolution section in Route Handlers ( #72222 )
...
This PR fixes issue on the [Route
Handlers](https://nextjs.org/docs/canary/app/building-your-application/routing/route-handlers )
documentation page:
Missing switcher for TS codeblock in [Route
Resolution](https://nextjs.org/docs/canary/app/building-your-application/routing/route-handlers#route-resolution )
section.
<!-- 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 >
2024-11-07 09:11:15 +00:00
2211fd2b69
Docs: Vitest: Support for import aliases when using TypeScript ( #72430 )
...
Related to https://github.com/vercel/next.js/discussions/72424 .
I wasn't able to test if the added "Terminal" switcher works, because I
don't know how to run the docs locally.
<!-- 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 >
2024-11-07 08:45:45 +00:00
3b5b5a25a9
docs(output): update standalone docs with cp and start commands ( #72432 )
...
## Why?
We're not documenting a way to manually move files to `.next/standalone` for `output: 'standalone'`.
2024-11-06 14:50:14 -08: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 <hello@richardhaines.dev >
2024-11-06 12:32:05 +00:00
Philipp Parzer