-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ModuleNotFoundError when using @import-s in CSS #48
Comments
:) |
I guess it is a bug related to browserify/resolve#177 I also created a temporary bug fix for |
Well I was just using Mini CSS Extract Plugin in the meantime. Tried your fix but it didn't really work, got the same error. But maybe my setup was wrong. |
This is still broken in the same way with the latest version (5.1.0). Applying the fix in https://github.com/malash/extract-loader/commit/37f4feb80d69d011754b8b01424248e2128c4e27 does not seem to change anything I created an up-to-date test case in https://github.com/Artur-/extract-loader-import-fail |
I get the below error when using
extract-loader
aftercss-loader
. It seems that it messes up relative paths and wants to find a module by one folder higher in the path hierarchy - butcss-loader
is working fine, if you comment outextract-loader
in the Webpack config file you can see its output in thedist
folder.Please advise. Here's a tiny repro repo:
extractLoaderCssError.zip
Just install with NPM and then run
webpack
to see the error.Am I doing something wrong or is this
extract-loader
's fault?The text was updated successfully, but these errors were encountered: