-
Notifications
You must be signed in to change notification settings - Fork 219
Long time to process image during gatsby develop #240
Comments
This is possible, but would require an upstream change in gatsby-source-shopify. What size are your Shopify images? If the originals are huge it might slow things down. (The Gatsby builds are only a few seconds for image processing, for comparison.) |
@wardpeet is working on a fix for this gatsbyjs/gatsby#10964 |
Just around 80 jpg files, 2k x 3k pixels each, it really takes sooooooo long time to start the develop process. |
Guess this is exactly what I m looking for right now. |
Hi,
yes, I still need to figure out a few ruff edges so we are sure our caching
of assets is kept in tact when switching between develop & build.
I'll keep you posted
Regards,
Ward
…On Wed, Jan 16, 2019 at 3:11 PM gddabe ***@***.***> wrote:
@wardpeet <https://github.com/wardpeet> is working on a fix for this
gatsbyjs/gatsby#10964 <gatsbyjs/gatsby#10964>
Guess this is exactly what I m looking for right now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#240 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABEanusnNuAM2UFAiZM3Q2l5BsWyJBAwks5vDzMmgaJpZM4Z9qrq>
.
|
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! 💪💜 |
Keep it open @gatsbot I'm experiencing this issue |
@wardpeet did this patch get merged? I haven't seen the slow image process, so I can’t verify. |
On my Macbook air 2018, it takes forever and stuck on gatsby develop. On my iMac it works but almost take 30mins on gatsby develop.
Is it possible to skip processing image during development and leave it turn on only on gatsby build for production release?
The text was updated successfully, but these errors were encountered: