> "now Gatsby inlines ALL of the site's css in each and every page" Did this abruptly happen at some point? It happened in gatsby @2.1.3 (a minor "patch" relea

> "now Gatsby inlines ALL of the site's css in each and every page" Did this abruptly happen at some point? It happened in gatsby @2.1.3 (a minor "patch" release!) [1] > would probably try next.js next time just to know what I've been missing. Have you worked with it before doing similar stuff? Not at the same scale. However, just reading their docs gives me way more confidence in that they are explicit about what the thing does or doesn't do. For instance, they can do prerendering like gatsby but there are many warnings about it in the docs [2], and you can always fall back to per-request SSR on any page if prerendering doesn't work there. Also it does away with the whole graphql thingy (you just get a `fetch` that works both server-side and client-side) and call the "backend" api directly. [1] https://github.com/gatsbyjs/gatsby/issues/11072 https://github.com/gatsbyjs/gatsby/issues/11072 [2] https://nextjs.org/docs#automatic-prerendering https://nextjs.org/docs#automatic-prerendering