-
Notifications
You must be signed in to change notification settings - Fork 8
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
forceGenerateImages and non-existent images #15
Comments
Hi @Jesus82. Thank you very much for the compliment. It's good to hear that this module is proving useful! Do you know if this is still an issue? I haven't tried the test case where source images may be missing. When I get time I'll check in and see if I can duplicate this. Thanks, Barry |
Hi Barry, I can confirm I have this problem also if I remove some of the source files – say if they are declared in a JSON file somewhere and used by the app. I get this warning for every size of the first missing image, the the process stops with a
This would be very helpful! Best, Simon |
Got the same issue! Subscribing |
…ils when source file doesn't exist.
Please try a fix I just added to a new release 1.4.1 and let me know generating images works for you. I added a check to see whether the source file exists and if it doesn't it skips generating that particular image and displays a warning at the console for each file that may be missing. E.g. |
Hi, first of all, big thank you for this component, it really brings the best of gulp processing-style into nuxt.
I'm facing an scenario where I
npm run generate
withforceGenerateImages
and some of the "original" images can be missing. If that happens, the generate process stops. Is there any way to let the generate process run even if there are some missing images?The text was updated successfully, but these errors were encountered: