-
Notifications
You must be signed in to change notification settings - Fork 132
Unable to load image files #51
Comments
I'm having that same issue |
Found the solution as random as it seems its all fixed by running |
Same issue, @Mike3run fix, resolved it. Stinks this has to be done. |
I had the same issue on Ubuntu 16.10. Apparently, they removed libpng12 in favor of libpng16? |
This looks similar to imagemin/imagemin-mozjpeg#23 |
The true reason is found here: imagemin/mozjpeg-bin#18 |
this solution worked for me. Thank @Mike3run |
Is this "the new normal"? Will this be documented in the readme? |
It would be nice if someone could document this issue in the readme and submit a PR. |
I'll close this for the moment. It's not fixed but it's documented in the README (see #66). Thanks @modernserf |
@Mike3run thanks. I dunno how that brew install libpng fixed it but it did |
seriously... that's crazy. random af but THANK YOU |
brew install libpng did not work for me. are there other suggestions? |
@jamesont why don't you paste whatever the console spitted out so we can take a look. At least the libpng thing was like that for me and several other people here, its usually right there but we don't read it the first time 😝 We can figure this out together |
Thanks @Mike3run ! Just a sec while I run build. Ok here ya go: |
I think that error has nothing to do with this plugin it says can't resolve So maybe you did a require or import to the wrong place... Protip its the 2 chunks of red text, you'll see more info there 😄 |
@Mike3run Thanks mike. I've tried a million things, I'm not sure where to go. This is actually from a Udemy course I've been taking online, and I've checked and re-checked the code. Can't figure out what the problem might be. I've tried messing with those file paths; nothing seems to help. |
@jamesont, I'm doing the same course on Webpack 2.0 ... something in homebrew is broken. |
@kenguie just to clarify webpack has nothing to do with libpng aka this doesn't mean webpack is broken not even an issue of this loader even since this is only a thin wrapper on |
Thanks Ken, but I've tried brew install libpng and that had no effect. Any
other suggestions?
- Thomas
…On Sat, Mar 11, 2017 at 11:21 AM, Ken Guie ***@***.***> wrote:
@jamesont <https://github.com/jamesont>, I'm doing the same course on
Webpack 2.0 ... something in webpack is broken.
run- brew install libpng
and it should all work after that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANsJ--AA1cHKCHR_k6ywWT2Wz_i1vx-uks5rkvQ4gaJpZM4KhgRP>
.
|
Just saw this message - did you mean homebrew install libpng?
…On Sat, Mar 11, 2017 at 11:41 AM, Ken Guie ***@***.***> wrote:
Sorry, mistyped - meant to say homebrew ... I was trying to give u a note
and move to the next lesson :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANsJ-_tAUaSnqXj12RSLJGvb5dT7Mlajks5rkvj8gaJpZM4KhgRP>
.
|
Thanks Miguel,
Can you be more specific as to where to look with imagemin?
Thanks,
Thomas
…On Sat, Mar 11, 2017 at 11:35 AM, Miguel Palau ***@***.***> wrote:
@kenguie <https://github.com/kenguie> just to clarify webpack has nothing
to do with libpng aka this doesn't mean webpack is broken not even an issue
of this loader even since this is only a thin wrapper on imagemin so your
concerns should be directed there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANsJ-1Ip0EvyvdPNgEppqp99nKrUqojJks5rkveYgaJpZM4KhgRP>
.
|
Awesome, I'll try that out and keep you posted. Thanks!
- Thomas
…On Tue, Mar 14, 2017 at 2:00 PM, Miguel Palau ***@***.***> wrote:
imagemin/imagemin#234 <imagemin/imagemin#234>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANsJ-09D5TgqwyWs6OLGRGrDAhpekMY8ks5rlv_WgaJpZM4KhgRP>
.
|
I actually just typed 'brew install libpng' and after that according to my history I ran 'npm run build' and it all worked out. I had the same errors though before that. |
I don't have administrative privileges on the remote Red Hat build machine I am using in our environment. Why do I need to install a system-level binary to make image-webpack-loader play nicely with Node/NPM/Webpack? This should not be the case. Has anybody looked into the long-term solution for those of us who cannot simply install libpng? Any help would be appreciated. |
@forgo not use this package? just go with normal file loader, this also adds an extra cpu bourden, you could process the images on your computer first and be done with it |
Will it be resolved or the only way to get it to work is |
I solved this same issue installing 'libpng' as @kenguie said, and then installing the file-loader module: After that I ran 'npm run build' and everything worked ok! |
Thank you!
…On May 13, 2017 6:34 PM, "Camilo" ***@***.***> wrote:
I solved this same issue installing 'libpng' as @kenguie
<https://github.com/kenguie> said, and then installing the file-loader
module:
'npm install file-loader --save-dev'.
After that I ran 'npm run build' and everything worked ok!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANsJ-_UO-Mdea3gmfCxs1e_FjApgcETfks5r5lo8gaJpZM4KhgRP>
.
|
Resolved my issue with .....brew install libpng ..thanks @Mike3run |
chenyiqidembp# brew install libpng curl: (22) The requested URL returned error: 404 Not Found I don`t know how to init libpng |
Still fixing the problem one year later 👯♂️ |
I did this two things (based on previous comments): |
In addition to |
After upgrading to 3.0.0, I'm getting this error:
This error doesn't happen on the 2.x.x version.
The text was updated successfully, but these errors were encountered: