-
Notifications
You must be signed in to change notification settings - Fork 141
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
Drop the Ruby dependency #31
Comments
The way I envisioned (and implemented) the original contrib series was as monolithic set of official plugins. Eventually it became clear that they should each be their own individual project. When I broke them out into separate repos it was no longer an issue for some of them to have non-js requirements. |
So there is no plan for grunt-sass to get merged into grunt-contrib-sass in the near future? If so, that's fine... I guess I'll just use grunt-sass instead. The allure of the "grunt-contrib-*" name brought me here first, of course. |
That would be a question for @sindresorhus--he maintains this repo. On Apr 18, 2013, at 10:02 AM, "James M. Greene" [email protected] So there is no plan for grunt-sass to get merged into grunt-contrib-sass in — |
Ouch, GH mangled that email response. @sindresorhus Thoughts? |
@JamesMGreene not in the foreseeable future. libsass (which node-sass uses) is missing a lot and node-sass has been nothing but trouble. This task is pretty stable now. If you want to take the chance on something faster, but more buggy and less features you can always use grunt-sass. But for most, stability and features are the most important things. And why are you basing your "no Windows support" argument on a 7 month old closed issue. |
@sindresorhus: I never said "no Windows support", just that it wasn't explicitly supported. See this comment on sindresorhus/grunt-sass#7 (comment) for a little more detail. |
So how is it that this grunt-contrib task came to be using Ruby despite all of the opposition in gruntjs/grunt-contrib#12?
I know Sindre has grunt-sass, which utilizes node-sass but that also doesn't explicitly support Windows (see sindresorhus/grunt-sass#7) due to intermittent support for Windows in node-sass... which I'm confused about: looking at sass/node-sass#10, looks like this should've been covered by PRs sass/node-sass#31 and sass/node-sass#82.
cc: @tkellen @sindresorhus @teabass @deanmao
UPDATE: Correction: @andrew (not @teabass)
The text was updated successfully, but these errors were encountered: