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
{{ message }}
This repository has been archived by the owner on Jul 9, 2020. It is now read-only.
It would be rad if zeta had decent integration with scss. Right now scss is useless as a standalone tool because it doesn't resolve imports like Sass. If zeta would be able to parse the imports, pass the generated output to scss and then put scss's output into a specified output file, zeta would become a lot more useful.
Another option would be allowing zeta to print to stdout and being able to pipe that through scss (i.e. make it read from stdin and print to stdout or into a specified file).
zeta and scss are neat and a step in the right direction to allow Sass-users abandon Ruby for good, but the lack of integration (and zeta's reliance on prefixes rather than output paths) are why django_compressor forced me to go back to Sass.
The text was updated successfully, but these errors were encountered:
It would be rad if zeta had decent integration with scss. Right now scss is useless as a standalone tool because it doesn't resolve imports like Sass. If zeta would be able to parse the imports, pass the generated output to scss and then put scss's output into a specified output file, zeta would become a lot more useful.
Another option would be allowing zeta to print to stdout and being able to pipe that through scss (i.e. make it read from stdin and print to stdout or into a specified file).
zeta and scss are neat and a step in the right direction to allow Sass-users abandon Ruby for good, but the lack of integration (and zeta's reliance on prefixes rather than output paths) are why django_compressor forced me to go back to Sass.
The text was updated successfully, but these errors were encountered: