rsnext/docs
Hofer Ivan 9ab6ca5d5f
chore(docs): add typesafe-i18n as a new i18n option (#47315)
<!-- 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 or adding/fixing 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 #

-->
2023-03-31 11:28:28 -07:00
..
advanced-features chore(docs): add typesafe-i18n as a new i18n option (#47315) 2023-03-31 11:28:28 -07:00
api-reference chore(docs): update next export to output: 'export' (#47717) 2023-03-31 02:04:23 +00:00
api-routes chore(docs): update next export to output: 'export' (#47717) 2023-03-31 02:04:23 +00:00
basic-features Update Error Boundaries link to new ReactJS documentation (#47474) 2023-03-24 04:12:33 +00:00
guides Update building-forms.md (#44862) 2023-01-13 14:34:55 -08:00
migrating chore(docs): update next export to output: 'export' (#47717) 2023-03-31 02:04:23 +00:00
routing fixed missing <Link /> keyword (#42422) 2022-11-03 11:07:01 -07:00
accessibility.md Add documentation on accessibility. (#38522) 2022-07-14 13:05:39 +00:00
authentication.md Alphabetize auth docs providers. (#34281) 2022-02-13 00:51:53 +00:00
deployment.md Linking to SST Next.js tutorial. (#47752) 2023-03-31 17:13:31 +00:00
faq.md doc: improve a word client side rendering (#39771) 2022-08-22 14:55:46 -05:00
getting-started.md Update getting-started documentation (#45284) 2023-01-26 01:25:42 +00:00
going-to-production.md Fix URL anchor position in going-to-production.md (#47056) 2023-03-13 06:01:37 +00:00
manifest.json chore(docs): add snippets for common image loaders (#46647) 2023-03-01 17:19:28 -05:00
testing.md Switch to ESM Jest config in docs (#42144) 2023-03-28 00:10:58 +00:00
upgrading.md Docs: next/font updates (#46159) 2023-02-24 05:20:26 +00:00