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.

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]: Rewrite in Next.js App Router #2195

Open
IncognitoTGT opened this issue Aug 31, 2024 · 0 comments
Open

[proposal]: Rewrite in Next.js App Router #2195

IncognitoTGT opened this issue Aug 31, 2024 · 0 comments
Labels
question Further information is requested

Comments

@IncognitoTGT
Copy link

Summary

Quran.com currently uses Next.js Pages router on Next.js 12, which is an outdated version. The Pages Router is also not the latest routing method for Next.js and is missing some features that I think would make the website better, faster, and also simplify the development workflow.

Next.js App Router has a couple benefits, such as:

  • Less JS loaded per page
  • Less confusing routing, and simplified data fetching (directly in the react component, instead of a seperate function)
  • Fully SSR'd pages for less resource intensive pages, requiring less JavaScript
  • Less API routes and simpler form submissions. now has a action prop that gets FormData passed as an argument, and you can use server actions (JS functions that can be executed from the server and called from the client) instead of extra API routes
  • Component streaming, allowing components be partially loaded and get sent to the client faster.

And other things:
https://nextjs.org/blog/next-13

https://nextjs.org/docs/pages/building-your-application/upgrading/app-router-migration

@IncognitoTGT IncognitoTGT added the question Further information is requested label Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant