Upgrade site from pages router to app router #472
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: johan <[email protected]>
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate the Next.js site from Pages Router to App Router to leverage Next.js 14 features and improve site architecture.
This migration involved creating the new
appdirectory structure, converting all pages and API routes to the App Router paradigm, updating data fetching mechanisms (fromgetStaticProps/getServerSidePropsto async server components), replacingnext-seowith the built-in metadata API, and adapting client-side components with'use client'directives. Navigation hooks were updated fromuseRoutertousePathname/useParams, and old Pages Router files were removed. The build currently compiles successfully, but some pages may still encounter runtime errors due to component compatibility issues.