-
Notifications
You must be signed in to change notification settings - Fork 8
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
Be able to use ruby sass instead of sassc #12
Comments
Sounds like @alandipert is also interested in working on this. |
For the record, I'm totally open to this, but I also wonder if the differences are enough to warrant a different task? (boot-sass versus boot-sassc) Or if the differences of pulling in JRuby + gem aren't really that bad due to pods, we could support both and only load what the user really wants at runtime? |
@mathias given currently it uses sassc as external executable, there might be no need to pull in JRuby - just ask user to install sass/compass as plain ruby gems if they wish to use sass |
The reason I'm interested in sass gem in a pod is so that our application can depend on a version of sass. Developers have been installing different versions of sass (sass gem, sassc from source, sassc from docker, etc) with mixed results. If we could pin our projects to a version of sass, team development on the project would be easier. I agree that shelling out is also useful and I like the idea of doing either, depending. I'll work more on it and report back here with results. |
I found this project trying to integrate stylesheet build step into our project's boot setup, but our styles use Compass, which heavily depends on ruby sass compiler and cannot be built with libsass (sass/libsass#82, Compass/compass#1916).
It'd be awesome if boot-sassc can be configured to use sass instead of sassc.
The text was updated successfully, but these errors were encountered: