Is app router ready for production
Unanswered
RS posted this in #help-forum
RSOP
Hi,
I’m building a new project in my company and was planning to use nextjs app router for it but I’m listening and reading alot of bad comments for this. so should i use app router is production app?
Need help on this
I’m building a new project in my company and was planning to use nextjs app router for it but I’m listening and reading alot of bad comments for this. so should i use app router is production app?
Need help on this
8 Replies
it is ready for production use
Asian paper wasp
Vercel is declaring it is stable.
However, it depends on the canary version of React. So it is not the kind of "stable" people usually expect. Now since it is for your company, you may wanna discuss this with your team on the cost and benefits of whether to use it.
P.s. Page Router is always a thing and is still working as it used to ve
However, it depends on the canary version of React. So it is not the kind of "stable" people usually expect. Now since it is for your company, you may wanna discuss this with your team on the cost and benefits of whether to use it.
P.s. Page Router is always a thing and is still working as it used to ve
RSOP
currently we are using page router for our other projects
Seo and performance matters alot for us on this project
will it be compromised with app router?
Seo and performance matters alot for us on this project
will it be compromised with app router?
It won't be
App Router can be faster because it adds support for streaming and react server components
Of cause that depends on your requirements and features
I tried to visualize it here: https://scroll-animation-streaming.vercel.app/ (best viewed on desktop chrome)
Of cause that depends on your requirements and features
I tried to visualize it here: https://scroll-animation-streaming.vercel.app/ (best viewed on desktop chrome)
@Asian paper wasp Vercel is declaring it is stable.
However, it depends on the canary version of React. So it is not the kind of "stable" people usually expect. Now since it is for your company, you may wanna discuss this with your team on the cost and benefits of whether to use it.
P.s. Page Router is always a thing and is still working as it used to ve
That's only partially true
Wether a React version is
Wether a React version is
stable to use is defined by Meta and Meta says Canary is stable for frameworks:Canary release channel for React [...] is officially supported [...] we’ll treat them with a similar urgency to bugs in stable releasesSee: https://react.dev/blog/2023/05/03/react-canaries
React Canaries only include features that we reasonably believe to be ready for adoption. We encourage frameworks to consider bundling pinned Canary React releases
@jantimon That's only partially true
Wether a React version is `stable` to use is defined by Meta and Meta says Canary is stable for frameworks:
> Canary release channel for React [...] is officially supported [...] we’ll treat them with a similar urgency to bugs in stable releases
>
> React Canaries only include features that we reasonably believe to be ready for adoption. We encourage frameworks to consider bundling pinned Canary React releases
>
See: https://react.dev/blog/2023/05/03/react-canaries
Asian paper wasp
Meanwhile, in the same paragraph you quoted:
Also, when mentioning React frameworks:
Again, both architecture has its pros and cons (I'm using App for my website and Pages for my corporate website). And it is up to the OP to decide which one is better suited for them.
But I feel that I need to re-state this, as this is something that seems to be overlooked by quite a few people:
Canaries let you start using individual new React features before they land in the semver-stable releases.
Also, when mentioning React frameworks:
Bleeding-edge React frameworkshttps://react.dev/learn/start-a-new-react-project#bleeding-edge-react-frameworks
The Next.js team has agreed to collaborate with us in researching, developing, integrating, and testing framework-agnostic bleeding-edge React features like React Server Components.
These features are getting closer to being production-ready every day** (in other words, according to the React core team's standard, it is not yet ready today), and we’ve been in talks with other bundler and framework developers about integrating them.
Again, both architecture has its pros and cons (I'm using App for my website and Pages for my corporate website). And it is up to the OP to decide which one is better suited for them.
But I feel that I need to re-state this, as this is something that seems to be overlooked by quite a few people:
Vercel is declaring it is stable. However, it is not the kind of "stable" people usually expect.
This is already ignoring the fact that some decisions made to the current version of the App Router are clearly mistakes, properly due to the fast-paced delivery schedule, and the Vercel team knows about that and actually implemented experimental features (in a no so stable architecture) to fix those issues.
This is something that is pretty much expected for a "new" framework but not so much for a mature, "traditionally" production ready one.
This is something that is pretty much expected for a "new" framework but not so much for a mature, "traditionally" production ready one.