Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration
by pdimitar on Tuesday May 12, 2020 @12:43AM
(#23150650)
What's the difference between `next build` and `next export`? I couldn't tell from reading your comment.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration
by cprecioso on Saturday May 23, 2020 @12:13PM
(#23284113)
`next build` makes a server that needs to be run with nodejs. Dynamic pages keep being JS code. the fact that some pages are optimized down to html is an internal implementation detail.
`next export` makes a folder of static resources (HTML, packages client JS code, CSS). It also forces every page (even dynamic ones) to compile down to HTML.
- `next dev` starts the dev server with unoptimized code and webpack hot-reload
- `next build` compiles all your code to be ready for production (optimizations enabled and not hot-reloading, pages that aren't dynamic server-side get turned into regular HTML, etc)
- `next start` serves that production-ready bundle, with a bare-bones (but production-ready) server
- `next export` forces every page to compile down to HTML and gives you a folder of static markup and js you can upload to any static host
So yeah, `next start` is indeed production-ready, and similar to what major websites already do. (Also there's no soft, hard, or default dependency between webpack and react, but the starter template uses it to make life easier for devs)