Framework built on top of React.
Officially recommended by *.
Puts lots of emphasis on server-side rendering just working, which looks good.
It does feel like they don't document deployment very well however, especially non-Vercel options, which is the company behind Next.js.
And until the prerender upload location issue mentioned below is answered clearly, Ciro Santilli just can't go for this option.
In order to offer its amazing features, Next.js is also extremelly opinionated, which means that if something wasn't designed to be possible, it basically isn't.
No prerender with custom server? It forces you to write your API with next as well? Or does it mean something else?
TODO can it statically generate pages that are created at runtime? E.g. if I create a new blog post, will it automatically upload a static page? It seems that yes, and that this is exactly what Incremental Static Regeneration means:
However, Ciro can't find any mention of how to specify where the pages are uploaded to... this is pat of the non-Vercel deployment problem.
ISR was basically unusable for CRUD websites because you can't force a one-off immediate page update:
Can't prerenter by URL query parameters:
- https://www.reddit.com/r/reactjs/comments/8evy5d/what_are_the_downsides_to_nextjs/ 2017 What are the downsides to Next.js?
- React | 37, 302, 1