-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Production ready? #15
Comments
One of its goals is definitely to be production ready, but since it didn’t reach version 1.0 yet, there may be breaking changes in the future, see #8 for example. If you want to use it in production you should use the PostCSS plugin and check your CORS settings to get the best performance. |
Thank you sir! That really helps. It's certainly tempting even with the risk of things changing. I'll play around with it. Looking forward to see where things go with this project. |
I've been using this in a few projects just fine. Just had to create a Sass function for parsing the container query rules. |
@rask Awesome, thanks for chiming in to confirm. So would your Sass function be an alternative to the PostCSS plugin then? |
@rohmann Kind of yeah, I'm using just the prolyfill and running the Sass function to parse the classnames for the Sass->CSS conversion (instead of Sass->CSS->PostCSS). I made a Gist to show how I did it: https://gist.github.com/rask/434e96f603e8b439dc64 That function may need updating later on in case the syntax changes. I needed that for simple width/height defined container queries so there may be cases it doesn't work right. |
Nice! Thanks for sharing that :) |
Love where you're going with this.
Would you say this is more experimental? Or is there confidence in it being production ready?
The text was updated successfully, but these errors were encountered: