You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all: Thanks for this pretty elegant way of having CSS in JS!
I used csjs-extractify and the css files generated are correct. But the css is still inside the browserify bundle. Therefore the JS bundle will still be the same size (plus the generated CSS) and there will also be a runtime overhead.
This following behaviour is what i would have expected.
Yeah, this is a known issue and was one of the things brought up in #3 but it's somewhat difficult to do statically at build-time. That said, what you are describing is definitely possible to do but I haven't had a chance to implement it yet 👍
I agree that it's not possible with static analysis in every possible way the code might look like. Once this is implemented, there should be a note on that in the readme that you can only access the class names after transpiring, not more.
First of all: Thanks for this pretty elegant way of having CSS in JS!
I used
csjs-extractify
and the css files generated are correct. But the css is still inside the browserify bundle. Therefore the JS bundle will still be the same size (plus the generated CSS) and there will also be a runtime overhead.This following behaviour is what i would have expected.
The text was updated successfully, but these errors were encountered: