-
-
Notifications
You must be signed in to change notification settings - Fork 608
Next #760
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
Next #760
Conversation
Looks node on |
what the hell with CI 😕 |
3766e86
to
93ae399
Compare
Ideally we extract the needed |
Hashes are not platform consistent to my knowledge, but maybe it was fixed in newer version of |
@michael-ciniawsky wip on updating |
8f7507d
to
2c2c757
Compare
/cc @michael-ciniawsky CI green (problem in deps also fixed) |
Just gave this a quick testrun, and I ran into the following error:
Full testcase can be found at https://git.cryto.net/joepie91/icss-loader-test. This compiled 'correctly' with I tested it against |
On closer inspection, it also seems to not support CSS Modules? Or at least the There doesn't seem to be any option to enable support for this either, and the option for specifying a class name ident format has also disappeared in this release. |
For |
@joepie91 old css modules doesn't work with next css modules (ICSS) in some cases, you can find example with css modules in README |
@joepie91 also you have invalid code you try to import class, but no export |
Hmm, the ICSS spec suggests that you should only specify exports for exported literals, not for class names?
(Emphasis mine.) How does that combine with having to explicitly export classes? Given that those are presumably not literal strings. |
@joepie91 to avoid big size of |
b4e8250
to
407b651
Compare
All in master |
What kind of change does this PR introduce?
bugfix, feature, refactoring
Did you add tests for your changes?
Yes
If relevant, did you update the README?
Yep
Summary
Rewrite
css-loader
Does this PR introduce a breaking change?
Yes