ce4d40b00b
fix(docs): Fix links in UPGRADING.md ( #84114 )
...
### What?
Both links in this file were broken/out of date.
### Why?
### How?
Updated with new links, open to suggestions if we want to link
elsewhere!
Co-authored-by: Joseph <joseph.chamochumbi@vercel.com >
2025-09-23 12:23:16 +02:00
a2cba246fa
docs: Fix link on UPGRADING.md ( #75761 )
...
### What?
Fix the upgrade instructions in `UPGRADING.md`.
### Why?
The `/docs/02-app` path does not exist.
---------
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2025-02-19 22:34:47 +00:00
bca1972f6f
docs: update broken link in UPGRADING.md ( #70107 )
...
## Description
At #60388 , upgrading.md was moved.
Then update the link to correct directory.
❌
[/docs/02-app/01-building-your-application/10-upgrading](https://github.com/vercel/next.js/blob/canary//docs/02-app/01-building-your-application/10-upgrading )
✔️
[/docs/02-app/01-building-your-application/11-upgrading](https://github.com/vercel/next.js/blob/canary//docs/02-app/01-building-your-application/11-upgrading )
### 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
x-ref: #60388
<!-- 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
### 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 >
2024-09-16 19:24:42 +00:00
6568502dcf
docs: update broken link in UPGRADING.md ( #60342 )
...
This link →
[/docs/02-app/01-building-your-application/09-upgrading/index.mdx](https://github.com/vercel/next.js/blob/21452921c055421ec8a44dae6e0e5f311c503337/docs/02-app/01-building-your-application/09-upgrading/index.mdx )
doesn't exist.
Fixing it to link to the correct directory.
Closes NEXT-2006
2024-01-06 14:46:07 -08:00
5764c6e900
(Fix)Broken upgrading.mdx link ( #54234 )
...
Fixes #54223
2023-08-18 17:10:38 +00:00
709aac1e96
Move upgrading guide to /docs ( #10727 )
...
* Move UPGRADING.md to docs
* Add upgrading guide to manifest.json
* Update title
* Move to docs/upgrading
* Update UPGRADING.md
* Update docs/manifest.json
* Update UPGRADING.md
Co-authored-by: Tim Neutkens <tim@timneutkens.nl >
2020-02-28 23:46:18 +01:00
1937e7dcfe
Revert "Test"
...
This reverts commit a888bc7caf
2020-01-28 17:04:34 -08:00
a888bc7caf
Test
2020-01-28 17:03:03 -08:00
319bc463e7
Mention Custom App GIP in UPGRADING ( #8647 )
...
This tells the user to check their custom <App> for `getInitialProps` if they previously copied the example.
This should help them leverage automatic static optimization!
2019-09-05 22:37:22 -04:00
9ee4f049ff
contributing guide rename initialprops ( #8203 )
2019-08-01 11:55:53 -04:00
ac31f1636e
Add some notes about Now deployment ( #8205 )
2019-08-01 11:08:21 -04:00
273c6f0d66
docs: Document change concerning api-routes ( #8121 )
...
* Update UPGRADING.md
* Update UPGRADING.md
2019-07-29 11:12:29 -04:00
aac5121466
Apply missing formatting ( #8079 )
...
* Reapply missing formatting
* Fix lint
2019-07-23 14:33:49 -04:00
8078273a7f
Adding a note about babelrc ( #7897 )
...
* Adding a note about babelrc
Related to https://github.com/zeit/next.js/issues/7803
* Update UPGRADING.md
2019-07-11 13:36:05 -04:00
bd7a85e26f
Upgrade Doc: Note to remove @types/next ( #7830 )
...
* [doc] Add Uninstall @types/next in Upgrading Doc
* Apply suggestions from code review
Co-Authored-By: Tim Neutkens <tim@timneutkens.nl >
* Update UPGRADING.md
* Update UPGRADING.md
2019-07-09 13:37:30 -04:00
c650dca307
Note the config key is reserved ( #7840 )
...
Closes https://github.com/zeit/next.js/issues/7834
2019-07-09 13:03:37 -04:00
b900ad9b85
Note TypeScript migration ( #7787 )
2019-07-08 13:08:58 -04:00
6cc72052b8
Add UPGRADING doc ( #7773 )
2019-07-08 02:28:11 -04:00
Lachlan Campbell