We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Nobody want's to write their CSS strictly inside of a tagged template literal, let's make a first class CSS development workflow that just works.
There are two main options to consider here:
1. PostCSS Some Bazel specific rules exist here https://github.com/bazelbuild/rules_postcss but it's unknown what kind of shape they are in currently.
2. Sass Some Bazel specific rules exist here https://github.com/bazelbuild/rules_sass which as far as I know are in decent shape but subject to confirmation
Ideally, I would like to offer both as options rather than dictate one.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Nobody want's to write their CSS strictly inside of a tagged template literal, let's make a first class CSS development workflow that just works.
There are two main options to consider here:
1. PostCSS
Some Bazel specific rules exist here https://github.com/bazelbuild/rules_postcss but it's unknown what kind of shape they are in currently.
2. Sass
Some Bazel specific rules exist here https://github.com/bazelbuild/rules_sass which as far as I know are in decent shape but subject to confirmation
Ideally, I would like to offer both as options rather than dictate one.
The text was updated successfully, but these errors were encountered: