Skip to content
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

Proposal: Replace ruby based sass/compass for node-sass #514

Closed
knownasilya opened this issue Feb 25, 2014 · 6 comments
Closed

Proposal: Replace ruby based sass/compass for node-sass #514

knownasilya opened this issue Feb 25, 2014 · 6 comments

Comments

@knownasilya
Copy link

This is just a proposal. But it seems like it's always better to have less technologies involved if possible, and when building with Ember, not everyone is using Ruby, so it makes sense to use node-sass along with grunt-sass to do the compilation of SASS files.

What are other's opinions on this?

@stefanpenner
Copy link
Owner

unfortunately, i don't think node-sass has feature parity (especially lack of compass), so it will only be good for some users out of the box. (atleast for now).

I am open to a strategy that allows for either, based on the users preference.

@knownasilya
Copy link
Author

So maybe using node-sass if compass isn't being used, otherwise use grunt-contrib-sass?

@Pradeek
Copy link
Contributor

Pradeek commented Feb 25, 2014

I've had some issues building Bootstrap SASS with node-sass, though the same worked fine with grunt-contrib-sass which was supposedly due to some old version of libsass in node-sass. Until node-sass is ready for primetime, I'd stick to grunt-contrib-sass.

@knownasilya
Copy link
Author

@Pradeek good to hear. Did you by any chance submit an issue with node-sass about your issue? I think that'd be a good idea.

@Pradeek
Copy link
Contributor

Pradeek commented Feb 25, 2014

There is already an open issue in node-sass for this (sass/node-sass#233)

@stefanpenner
Copy link
Owner

although i share the ruby dep concern, i am unsure if this is really actionable for us today.

We can keep this issue around for discussion, but i am closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants