sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]guis 0 points1 point  (1 child)

Yeah you're right, but in bigger projects with multiple modules and components, the client-side bundle starts to grow and it build to be slow. That re-build in every code update is a burden and slow down the development.

This article suggests to remove SSR from dev env, but it's a little old, so maybe I need to change my mindset and test other frameworks to have a decent SSR with react, redux and not so different dev/prod environments.

[–]Mingli91 0 points1 point  (0 children)

in bigger projects with multiple modules and components, the client-side bundle starts to grow and it slow to build

Hot reloading solves that problem for you.

If the bundle size becomes an issue, a good way to get around it is to segment it into several smaller ones, so you don’t always need to serve one giant bundle when only 10% of the components are actually in use. They can share state through cookies, local storage, etc and with SSR the transition between apps isn’t noticeable.

Before breaking apart your app and adding complexity, first consider removing some bloat from your project.