Closed hashemian closed 6 years ago
I could resolve this issue by simply updating my node
and npm
. Before, I was using node 5.0.0
and npm 3.8.8
. When I updated them to node 8.11.2
and npm 5.6.0
, webpack works just as expected without any error. I'm unsure how updates to the node/npm helped though!
I do have package-lock.json
, but I could not find using my npm (v3.8.8), how I can enforce installing only based on that. I'm thinking maybe updating npm led to package-lock.json
being properly used and now things work again?
@hashemian sorry for the delay.
Firstly I suggest that you change resolve-url
to resolve-url-loader
.
You are in the very common situation where you use package resolve-url
and resolve-url-loader
. This will break webpack. I realise you didn't originate this config but pro-tip: always specify the full name of the loaders.
This is the source of hard-to-diagnose problems. So please fix that first and eliminate that as the root cause.
Thanks, Ben. I agree with your point. I read it elsewhere as well and changed the resolve-url
to resolve-url-loader
. But it didn't help. Eventualy, using a different node/npm version fixed the issue. Thanks for your comment.
Hi there,
I have a
webpack
config which converts somescss
files tocss
. The config was not done by me so I cannot describe the details, but here is how it looks like:My installed npm packages are the following:
It used to work just fine, but now that I checked out the project again, did an
npm install
and awebpack --progress
, here is my output:I could not find any
base64
in the css files generated up to that point, in case it could be similar to this issue. I also checked this issue, and the related patch. But it seems all versions ofpostcss
installed have this patch.Any idea what might be the issue? Thanks a lot.