4 ms·

"now Gatsby inlines ALL of the site's css in each and every page" Did this abruptly happen at some point? I've had attempts to migrate components from old repos

"now Gatsby inlines ALL of the site's css in each and every page" Did this abruptly happen at some point? I've had attempts to migrate components from old repositories cause similar issues and all I could see is that something with the dependencies of that project (e.g. "tree-model" definitely seemed to cause issues) were forcing gatsby to be overly safe in terms of culling CSS. Similarly we had issues with imports a component library, but upon inspecting other projects the same issue was happen with client side rendered apps, so it was down to how we built the library rather than Gatsby. My experiences were pretty positive but I did encounter every issue you've listed and would probably try next.js next time just to know what I've been missing. Have you worked with it before doing similar stuff? ------------- As far as Gatsby goes I think it occupies a definite niche but one that needs to communicated very effectively. You get: - static web pages - react ecosystem (very useful if all other company frontends are on react and there's a design system) - some webapp functionality The last one being key, more than _some_ and it's probably going to start becoming a headache juggling all the pieces.

kilburn 7y ago
> "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

kilburn 7y ago

> "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