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

Use node-sass? #38

Closed
cowboy opened this issue May 10, 2013 · 13 comments
Closed

Use node-sass? #38

cowboy opened this issue May 10, 2013 · 13 comments

Comments

@cowboy
Copy link
Member

cowboy commented May 10, 2013

Uses libsass, includes pre-compiled binaries for popular platforms, is probably 1000x faster and easier to set up than the current solution.

https://github.com/andrew/node-sass

(haven't used it myself)

@sindresorhus
Copy link
Member

@cowboy see #31

@bwilkins
Copy link

@sindresorhus, @andrew I have been working on improving node-sass, is there anything we can do to help?

@sindresorhus
Copy link
Member

@bwilkins the main problem isn't really with node-sass, but with libsass which is missing a lot.

It's missing both debug info and real sourcemaps. This PR says sourcemaps, but it looks like it's only debug info: sass/libsass#89

There's grunt-sass for those who want it. But I think the majority of people would still prefer something more feature rich and stable over fast.

@bwilkins
Copy link

Ohk, that's pretty much what I thought.

Do you know if there's a documented set of features missing from libsass? I'm mainly aware of the #{} variable interpolation issue that I believe comes from the ruby implementation, however I'm not certain if that's actually a feature of scss or people are just mistaking it for one.

@sindresorhus
Copy link
Member

@bwilkins no, but I think that could be very useful.

@robwierzbowski
Copy link
Contributor

But I think the majority of people would still prefer something more feature rich and stable over fast.

Exactly. Sass and Compass move pretty fast, and now that a big part of @chriseppstein's job is going to be working on Compass there will probably be more improvements than usual. Being able to use the official library is a big benefit IMO.

@bwilkins
Copy link

Perhaps what this ticket should be is a note to look at ease-of-use for this module? Ignore the part about speed (it's much of a muchness these days anyway) and just focus on the "easier to setup" part.

@sindresorhus
Copy link
Member

We'll definitely consider this in the future, but for now it's not stable or feature rich enough to be a feasible alternative. Use grunt-sass if you like playing on the edge.

@chriseppstein
Copy link

I agree that this would be premature at this time. However, my medium-term plans include helping get libsass to feature parity and making compass work with libsass in various application frameworks and languages.

@sindresorhus
Copy link
Member

@chriseppstein that's great to hear! :)

⬆️ @paulirish @addyosmani @passy @btford

@passy
Copy link

passy commented Jun 4, 2013

That's fantastic news indeed! It would be incredible if we could drop drop the ruby dependency at some point in the future for Yeoman.

@sindresorhus
Copy link
Member

We should consider doing some Bountysource on libsass to get more people involved.

@lmartins
Copy link

wow, just saw the comment from @chriseppstein
Would love to be able to use Compass with libsass, that would be perfect.

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

No branches or pull requests

7 participants