-
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
chore(gatsby-plugin-sharp): move image processing to a worker #19591
chore(gatsby-plugin-sharp): move image processing to a worker #19591
Conversation
…a… (gatsbyjs#19582)" This reverts commit 6f4b74d.
Can you point out the differences between this PR and #18934? |
Thanks! (this answer also known as "Mike, read the commit messages" 😅) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay! Thanks! 🎉
@wardpeet I have tried v2.3.2 and the total image gatsby tries to generate an increase from ~3000 to ~13000. This behavior starts to show up after I upgrade to the version above 2.3. |
@fodkastir, i'm not able to reproduce it. Might be just a visual bug. This should fix it #19717 |
I currently have a fix located at |
Description
Starting implementing new jobs api. Move logic to separate worker file so it can run in parallel.
Image processing didn't check the outputFile correctly so re-created all images all over again on each change.
Related Issues
Related to #18934
Fixes #19576