You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running gulp --stage=prod the images and image folder do not get copied over to the build directory although terminal output shows images finishing:
[01:37:51] gulp-imagemin: Minified 29 images (saved 57.88 kB - 6%) [01:37:51] Finished 'images' after 5.04 s
I'm also getting the following error in the browser console: Error: [jqLite:onargs] jqLite#on() does not support the selectororeventData parameters
Is there an issue with svg's? I also get a giant block of base64 output in the terminal during bowerCopy. Below is just an excerpt.
I've narrowed the image copy issue to the deleteTemplates task. I noticed you have '!' + config.buildImages in there twice. Deleting one of them still made no difference. It's ignoring your ignore statements. So for the time, I'm bypassing deleteTemplates and starting the build at copyTemplates.
I still trying to figure out the base64 garbage with angularjs-toaster/toaster.cssdata:image/png;base64.... Seems the bowerAssets task is choking on something in the bower_components/angularjs-toaster package. Is this just a poorly designed bower package?
I'm not familiar with how bower packages are processed by gulp so any insight / tips on how I might debug this is appreciated. Thanks.
When running
gulp --stage=prod
the images and image folder do not get copied over to the build directory although terminal output shows images finishing:[01:37:51] gulp-imagemin: Minified 29 images (saved 57.88 kB - 6%)
[01:37:51] Finished 'images' after 5.04 s
I'm also getting the following error in the browser console:
Error: [jqLite:onargs] jqLite#on() does not support the
selectoror
eventDataparameters
Is there an issue with svg's? I also get a giant block of base64 output in the terminal during bowerCopy. Below is just an excerpt.
A dev gulp build runs perfectly with no console errors. I'm using 0.8.3 with node 0.12.2.
And if I haven't mentioned it before, I've been using your gen since 10/2014 and loving it!!
The text was updated successfully, but these errors were encountered: