-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev: run image processing on demand #10815
Comments
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
i've put it to blocked as lot of efforts is already done but we need some kind of internal invalidation api so we know which nodes are valid. cc @pieh 😛 |
Going to close this in favor of #7348 |
Summary
Don't process all images in develop mode and only do it when it's needed (requested by browser).
Motivation
Booting up development server on large sites can take several minutes, because we wait for:
Those are needed to produce complete production builds, but we don't need all the images for development. We only need images that user is looking at and we can lazy generate them when browser requests them.
Details
This can be done by adjusting
gatsby-plugin-sharp
alone:For reference: this is split from #7348 (running queries on demand).
/cc @wardpeet
The text was updated successfully, but these errors were encountered: