Review NextJS and Remix to outline which framework to base our template on

[devraj]

NextJS is quickly catching up to cater for all aspects of React development, e.g data caching via SWR, routings etc. This is a ticket that's left as a reminder to keep an eye out on the developments of NextJS.

The main concern here is that Next as a framework does many things that a collection of frameworks are achieving.

Note that Orval is a key part of any solution we are exploring (we should possibly think about contributing to the project).

This would mean major refactor of the work we are undertaking at the moment.

[devraj]

Further to this, React's new documentation site suggests you choose a full stack framework and not use React directly as it does not prescribe how you handle things like routing.

Two of recommendations are Next and Remix, these articles do a good job at comparing them:

• A Look At Remix And The Differences With Next.js
• Nextjs vs Remix — Choosing the Right Framework
• Remix vs Next.js written by Ryan Florence

For what it's worth we are closely aligned with Remix (as we use React Router), however we still handle many of the other things like header management via other plugins.

This call for a serious review of the state of affairs and make a call on which way we should go, keeping in mind that this template is for building applications as opposed to web sites.