-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Support vanilla-extract styling #12771
Comments
Hm, sounds interesting. Ultimately, we can't support every method of styling though. Would someone be interested in maintaining a plugin for vanilla-extract? |
@FrozenPandaz volunteer here! I was thinking just about contributing to the official plugins to support vanilla-extract. Yet, how could it be approached with a separate plugin without having to change the build executor for an app or creating a custom webpack/rollup config file (why the plugin then)? |
This would be great. Any suggestion how to fix JEST not generating the styles?The suggested transformer is not working. |
Is there interest in building something around VE? |
See #12653 |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Description
Add native nx support for vanilla-extract styling
Motivation
Not sure what the ideology behind choosing which css libraries are used as options in nx or what criteria they must meet to be suppported natively.
Ive been playing around with vanilla-extract. I did a POC with it and nx and so far seems like a simple cohesion.
However, the custom webpack config is a bit hacky and could be improved by either supporting it natively or having a nicer way to add custom css webpack configs
Suggested Implementation
useful links:
The text was updated successfully, but these errors were encountered: