Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Build breaks with webpack 2, postcss and svg-inline
See original GitHub issueI’m submitting a bug report
Webpack version: 2.x
Please tell us about your environment: OSX 10.x
Current behavior:
With a specific file structure and when using postcss-loader, postcss-import and svg-inline-loader, I get the following error:
Module build failed: (SystemJS) ENOENT: no such file or directory, open '/Users/karolis/webpack-2-failing-build/loader-utils'
Expected/desired behavior: The build should work.
To reproduce
- Clone https://github.com/KidkArolis/webpack-2-failing-build
- Run
npm install && webpack --progress
I think the bug itself is caused by postcss-import, but this only happens in webpack@2, so I thought I’ll post here first and cross link to postcss-import repo. It would be nice to dive deeper and understand what’s causing this issue. It only seems to be happening with this very specific file structure. Moving the .css file around for example, might cause the build to work again. Any pointers on how to debug this further would also be appreciated.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yep, postcss-import somehow breaks webpack’s module resolution. It may be a bug with webpack’s SystemJS support, but for now the workaround is to pin postcss-import to 8.1.0.
Issue was closed because of inactivity.
If you think this is still a valid issue, please file a new issue with additional information.