-
Notifications
You must be signed in to change notification settings - Fork 281
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.
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
Proposal: Switch to app router of next.js #164
Comments
Sounds Interesting 😄 |
I think app router is not yet stable thus we should stick with pages directory. Also it offers features like getserverside props which is useful in protecting pages and middlewares. What do you think about this? @piyushgarg-dev |
@Your-Ehsan Hello sir, I know Next.js 13 but it's too complicated to convert your review-app directory routing into app routing can you please help me . because u have many files, components and subfolders it's very complex to identify I glad if u help me. |
@Umesh7Dixit Thanks for your interest. But at this time I just to confirm that If @piyushgarg-dev want this change in this project. |
If not solved can you assing me @piyushgarg-dev @thakurthegr8 |
Hey, We are planning to move to hybrid model. Today we have pushed the public form router under app/ dir and made use of server components. Thanks a lot for suggestions 😄💪 |
I'm glad you found my suggestion to convert the Next.js page router to an app router helpful. So, I think it's time to consider closing this issue. |
Proposal: I think that would be great if we switch the routing of our review app to the app router of next.js because it is easy to maintain and work with.
Currently it is working on page router.
I realized that the new comers who are at the learning phase in next.js are comfortable with nextjs's app router because it is now recommended by the next.js's community also.
your thoughts & suggestions are appreciate able
here's the nextjs's official guide
https://nextjs.org/docs/pages/building-your-application/upgrading/app-router-migration
The text was updated successfully, but these errors were encountered: