DEV Community

Discussion on: How to Disable Server-Side Rendering (SSR) in Next.js

Collapse
meglio profile image
Anton A.

In this scenario, what's the point in keeping using Next.js at all? No SSR, no routing, so why would one use this workaround and keep staying with Next.js instead of using something like create-react-app?

Collapse
hamzalak profile image
LAKHAL Hamza

Because you don't need SSR every time blog.usejournal.com/when-should-i-...

Collapse
apkoponen profile image
Ari Koponen Author • Edited on

Next.js is just better than create-react-app in many small ways. It has everything that create-react-app has and more in a very developer-friendly package.

One major thing I can mention that you never need to "eject" from Next.js the way you might need to do with create-react-app. You can customize your Webpack Config and be happy (nextjs.org/docs/api-reference/next...).

Also, even if you don't need SSR now, it does not mean you won't need it in the future. Using Next.js as your tooling will allow you to use SSR/SSG for some pages and normal client-side rendered behavior SPA for others.

Collapse
meglio profile image
Anton A.

So, the idea is to use Next.js but not its killer features because "just in case"?

Thread Thread
apkoponen profile image
Ari Koponen Author

What do you mean by not using Next.js's "killer features"?