search

gatsbyjs / gatsby

The best React-based framework with performance, scalability and security built in.
https://www.gatsbyjs.com
MIT License
55.27k stars 10.32k forks source link

question - incremental builds support = part II #5002

Closed ekdev2 closed 4 years ago

ekdev2 commented 6 years ago

4981

I think @LeKoArts is right. What I mean is if you generate a site with 2000 pages and deploy to aws, then one of those content pages changes in the cms, can you generate just that one page and deploy it.

lannonbr commented 4 years ago

With #21523 merged in and Incremental Builds available in Gatsby Cloud, I believe this issue is resolved. It doesn't support all workflows, but I am going to close this for now and it may be better to open a new issue in the future for future endeavors if need be.

agonsalves commented 4 years ago

Should it really be closed? The optimization was just that - an optimization. It wasn't truly incremental builds. On top of that, whatever is available through Gatsby Cloud is not available through usage of the public package. For the specific intent of this ticket, nothing has been resolved.

dandv commented 4 years ago

Should it really be closed?

Based on https://github.com/gatsbyjs/gatsby/issues/5496#issuecomment-641005662, I don't think this issue should stay closed, and I don't understand why the not stale label was removed.

datakurre commented 4 years ago

Has anyone here tried, or know if it is possible, to tweak GatsbyJS webpack configuration to simultaneously produce both development preview and production build version with ”gatsby develop”? (Possibly resulting ”incremental builds” with cost of forever running development server.)