score:154

Accepted answer

i've used both nextjs and cra. both these frameworks can be used to get started quickly and provide a good developer experience. however, both of these have use cases where either of them shines better. i'll try to compare them based on some of these factors. feel free to suggest edits with additional points or comments

server side rendering

cra next.js
cra doesn't support ssr out of the box.
however, you can still configure it.
it just takes more effort to setup ssr with your preferred server and configuration. the development team doesn't have plans to support this in the near future. they suggest other tools for this use case.		 nextjs has different types for ssr. it supports ssr out of the box.
* static generation: fetch data at build time. this works best for use cases like blogs or static websites
* server side rendering: fetch data and render for each requests. you have to do this when you need to serve different view for different users.

configurability

i think this is point where these tools are very different and your decision can depend on this factor

cra next.js
create react app doesn't leave you a lot of room to configure it.
configurations like webpack config cannot be changed unless
you stray away from normal cra way (eject, rescripts, rewired, craco).
basically, you have to use what's configured in
react-scripts which is the core of cra.		 almost everything is configurable.
if you check the example nextjs templates, you can see files like
babelrc, jest.config, eslintrc etc
that you can configure.

maintainability

cra next.js
cra is very opinionated.
if you keep updated with the releases of cra, it's not hard to maintain.		 nextjs is also well maintained. they release regular updates.

typescript

cra next.js
supports out of the box. you can initialize cra app with typescript with
npx create-react-app my-app --template typescript		 supports typescript out of the box.
start with configurations for typescript with touch tsconfig.json

hooks support

latest version of both cra and nextjs installs a version of react that supports hooks. you can also upgrade to the latest version easily

redux support

redux is a library that you can use with both these tools.

score:-1

react is a javascript library while next js is a framework that builds up on react and greatly enhances react apps and makes building large scale react apps easier, the main advantages of next js are the build-in server-side rendering (ssr) wich automatically pre-renders your page on the server and makes your app run much faster ssr also helps with seo optimization the next key feature is also its build-in file-based routing whereas in react you'd have to install the react router package and manually add the routes, next js also can be used as a backend where you can blend your backend and react code in the same project without having to create an api ,since it can do ssr it can also perform server-side code like store data, get data, authentication etc. personally i think next js is a very powerful tool that every react developer should master.

score:5

react is just a javascript library, and on the other hand, nextjs is a react framework. ssr is one of the benefits of nextjs, but there are many other benefits. nextjs can do everything react does, and on top of that, it has features that react alone doesn't have. checkout the documentation for nextjs here: https://nextjs.org/docs/getting-started

score:9

tldr

biggest difference is purpose of both projects. nextjs : jam stack or static site generator create react app : is an officially supported way to create single-page react applications.

explanation:

this conundrum is true for many opensource projects. seem alternative of other but they have key differences. for example in this case although both projects use reactjs as front end and produce webapps. the problem they solve are very distinct. there are some overlapping features themes/templates in js. but development and future work will be to enhance project such that it helps solve there problem statement in better way.

i.e. nextjs will try to include if there are any new markdown features developed. which won't be the case in createreactapps.

suggestion.

from your question it seems you are looking these projects for developing react native apps. so i will suggest go with create react app.

your comparison should primarily be whether this project align with problem i am solving. then compare. maintainability, scalability, typescript and react hooks/redux support.

in case needed more info do comment.

score:50

create react app is just a react project creation engine to help you setup your react project quickly. after running the cra script npx create-react-app <appname> you will get a nice and clean single-page application that you can run. under the hood you also get things like babel, eslint, jest, webpack already setup so it's a really convenient way to start doing react development. and in case you'd need more control over the configuration of those tools, you can still use npm run eject.

next.js on the other hand is a framework based on react to build node.js server-side apps. this means you will use the same component-oriented logic to build pages and leverage the next.js routing engine for page to page navigation. server-side rendering will allow loading time to be more spread over time, so perceived performance will be probably better. redux can be used as well but there will be some additional steps to make it work properly (see https://github.com/kirill-konshin/next-redux-wrapper)

whatever you choose, in the end, it will be react coding. components, jsx, typescript support, react hooks, and all other core aspects of react will be supported either way. therefore, you can expect similar degree of maintainability. on the other hand, scalability depends on your choice: if you choose next.js you will host the app on a server infrastructure which should be sized according to your audience whereas react bundle created with cra just need to be statically hosted somewhere.


Related Query

More Query from same tag