-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Issues with node-sass betas #44
Comments
Thanks for making this change, it's much appreciated. It's soooo close, but not quite there. It looks like you didn't push new info about broccoli-sass-source-maps@0.7.0 to npm. After
And indeed doing an
|
node-sass is now a peerDependency, so you specify which version of node-sass@3.x to use in your package.json file. |
Thanks @ZebraFlesh, that's published now. |
Many thanks! Everything works great now and I'm back in a happy place: I've got a stable sass build including bourbon mixins to support my terribly old FF 10 users (don't ask). Life is good. 👍👍 |
#40 and #43 are both a result of the node-sass@3.0.x-beta-x versions. I think that broccoli-sass should have gone to v1.0.0-beta-x version when it was upgraded to node-sass v3, but this didn't happen (and so I followed suit with ember-cli and broccoli-sass-source-maps). I now think this was a mistake, because several users have had to deal with failing builds without explicitly asking for a new version (see #40 and #43).
Here's what I've done to sort this out:
Please let me know if you're experiencing any issues with this. Hopefully this should allow people who want node-sass v3 to use the betas, and the rest of the world will just get a SASS compiler that works :)
The text was updated successfully, but these errors were encountered: