-
-
Notifications
You must be signed in to change notification settings - Fork 609
Description
Do you want to request a feature or report a bug?
It would be good to have an option to skip not found URLs instead of throwing "Module not found" errors.
It might be just a warning instead of critical error, or just skipped.
Ignoring all URLs and @imports, which is already supported - is not an option, since it's too global.
What is the current behavior?
When URL is not found it throws the error in following format:
ERROR in ./~/css-loader!./src/css/site.css
Module not found: Error: Can't resolve '../../node_modules/somelibrary/not-existing.gif'
This error eventually fails the whole webpack build.
What is the expected behavior?
If some options is enabled, such error becomes not critical and build is not marked as failed.
If this is a feature request, what is motivation or use case for changing the behavior?
Motivation is that when you rely on third-party library you cannot be sure they will include all files referenced in their vendor.css
. We are forced (corporate branding stuff) to rely on some internal (but still third-party library - i.e. different team responsibility), which works following some strange bureaucracy workflow and bad publishing practices. So not including all referenced files - is a common case..
Please mention other relevant information such as your webpack version, Node.js version and Operating System.
Would it be possible to implement such feature or are there any blockers why it wasn't made already so?
Or maybe there are other ways to achieve same thing?