Can't publish to Azure because of gifsicle, jpegtran, optipng. #112
Replies: 12 comments
-
|
What do you see in the Output window (There is a combo box in the output window, one of those items will tell us more about the error. Not sure which one based on your info). |
Beta Was this translation helpful? Give feedback.
-
|
The only combo box that seems to have anything relevant is the "Build" option. Here is the content from that window: 2>------ Publish started: Project: SMulholland.info, Configuration: Release Any CPU ------
2>Publish failed due to build errors. Check the error list for more details. |
Beta Was this translation helpful? Give feedback.
-
|
There seems to be a lot of npm related warnings. I wonder if that has anything to do with it. I have installed both with -g and I still see the same warning every time I attempt to publish. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Is there a specific node or npm version I should be using? I had the latest node.js installed on my system. I uninstalled it and installed the node version that comes from the VS installer as an optional install. Still nothing. |
Beta Was this translation helpful? Give feedback.
-
|
VS 2015 Update 3 with the .NET Core bits should be fine. I was going to tell you to check the readme where it tells you to delete the node and bower module folders, do a Looks like you are running into this issue for some reason: sindresorhus/gulp-imagemin#23 I'll investigate. |
Beta Was this translation helpful? Give feedback.
-
|
BTW, welcome to the horrible world of NPM packages where everything breaks for no reason and you have to go around reading GitHub issues to fix them :) |
Beta Was this translation helpful? Give feedback.
-
|
The gulp-imagemin I'm using is 3.10.5 after I ran npm install gulp-imagemin in my project directory. I changed the default package.json to that version as well. I didn't add image optimization to the default build... at least not on purpose. I've been trying a lot of different approaches. I'm not sure of anything any more. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, that will be it then. You need to use version 2.4.0 (I select versions of packages very carefully). If I remember correctly, above that version requires Gulp 4.0 which is currently unfinished but still in use by some: |
Beta Was this translation helpful? Give feedback.
-
|
I'm down to two errors on Publish:
Can you tell me which versions of optipng and jpgegtran I should be using. Changing gulp-imagemin to 2.4.0 removed 4 of the errors, but those two still persist. |
Beta Was this translation helpful? Give feedback.
-
|
Ok I've got it. In case anyone runs into the same thing. I had to run: which created the following in package.json under devDependencies: "dependencies": { |
Beta Was this translation helpful? Give feedback.
-
|
You shouldn't need those with 2.4.0. I suspect your NPM messed up while downloading the packages (Sadly this is fairly common and why I call it out in the ReadMe). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Using the .NET Core boilerplate. I'm trying to publish to Azure and getting the error below.
Things I've tried:
I've created a new project and still get the error. I ran 'optimize-images' Gulp task from the 'Task Runner Explorer' in Visual Studio. Still getting the error. Here is the output from 'optimize-images':
Beta Was this translation helpful? Give feedback.
All reactions