-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
sass-resources-loader and css-modules 'composes' #57
Comments
I am having the exact same issue. For now I have gotten it working by directly importing my sass variable files to the css module that defines the css class being composed. But that is exactly what sass-resources-loader is supposed to allow me to avoid.
|
@alexfedoseev Any idea on this one? |
It's simply doesn't work w/ CSS modules |
Geez, I'm not alone in this case. Same question here! |
webpack config { sass-resources-loader 'use strict'; var _fs = require('fs'); css-loader /* style-loader/css-loader/sass-loader, all of them can be loaded and running, but sass-resources-loader can not. |
for Less, even cannot use mixins. |
I've stumbled upon the very same issue when used compose and solved it having imported dependency file manually. Even though variables are defined on the both ends of composes rule - they get lost somewhere in the middle |
I'm having an issue when trying to use the css-modules functionality 'composes', like:
_vars.scss
type.scss
example.scss
the issue seems to be that at the time css-modules processes
type.scss
as part of the compose, the variables used in type.scss (which are otherwise used/available via sass-resources-loader when using a class from type.scss directly from js), don't seem to be available...or putting this another way, is there a way for sass-resources-loader to be making the vars from a settings file available to css-modules during it's
composes
functionality?Am I the only one who's tried to compose from a file that is dependent on sass-resources-loader enabled vars?
The text was updated successfully, but these errors were encountered: