You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
The React team no longer recommends CRA on the react docs (https://react.dev/), and instead recommends Next.js or Remix. Additionally, CRA can be extremely slow to load when used with TypeScript, is limited in its customizability, and lacks certain features that more robust frameworks offer.
Next.js offers an incredibly fast development experience, customizability (for instance, a Next.js app's babel configurations can be customized, which is not possible with CRA without CRACO or ejecting. This is important for using libraries such as Inversify.js which rely on experimental decorators), and powerful features such as code splitting which can lead to much faster load times for the user.
Migrating the application to Next.js will allow us to take advantage of all these features to improve user experience, improve developer experience, integrate TypeScript and Inversify.js to create a more type safe and testable app, and much more.
Goal
The goal of this issue is to use Next.js to bootstrap a new application and migrate the files from the existing application into this environment. Once completed, the app should be able to do everything it currently does, but it should depend upon Next.js instead of CRA.
The text was updated successfully, but these errors were encountered:
Problem
The React team no longer recommends CRA on the react docs (https://react.dev/), and instead recommends Next.js or Remix. Additionally, CRA can be extremely slow to load when used with TypeScript, is limited in its customizability, and lacks certain features that more robust frameworks offer.
Next.js offers an incredibly fast development experience, customizability (for instance, a Next.js app's babel configurations can be customized, which is not possible with CRA without CRACO or ejecting. This is important for using libraries such as Inversify.js which rely on experimental decorators), and powerful features such as code splitting which can lead to much faster load times for the user.
Migrating the application to Next.js will allow us to take advantage of all these features to improve user experience, improve developer experience, integrate TypeScript and Inversify.js to create a more type safe and testable app, and much more.
Goal
The goal of this issue is to use Next.js to bootstrap a new application and migrate the files from the existing application into this environment. Once completed, the app should be able to do everything it currently does, but it should depend upon Next.js instead of CRA.
The text was updated successfully, but these errors were encountered: