Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix broken link on the upgrading guide #42340

Merged
merged 2 commits into from Nov 2, 2022
Merged

Fix broken link on the upgrading guide #42340

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1b8e4cb
Fix broken link on the upgrading guide
mnajdova Nov 2, 2022
adf4c57
Merge branch 'canary' into patch-1
kodiakhq[bot] Nov 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/upgrading.md
View file
Open in desktop
Expand Up @@ -28,7 +28,7 @@ pnpm up next react react-dom eslint-config-next --latest

## Migrating shared features

Next.js 13 introduces a new [`app` directory](https://beta.nextjs.org/docs/routing/fundamentals) with new features and conventions. However, upgrading to Next.js 13 does **not** require using the new [`app` directory](https://beta.nextjs.org/docs/routing/fundamentals.md#the-app-directory).
Next.js 13 introduces a new [`app` directory](https://beta.nextjs.org/docs/routing/fundamentals) with new features and conventions. However, upgrading to Next.js 13 does **not** require using the new [`app` directory](https://beta.nextjs.org/docs/routing/fundamentals#the-app-directory).

You can continue using `pages` with new features that work in both directories, such as the updated [Image component](#image-component), [Link component](#link-component), [Script component](#script-component), and [Font optimization](#font-optimization).

Expand Down