Closed shivanibhanwal closed 9 years ago
You will need to specify 'broccoli-sass': '1.1.1'
in your package.json. If you have a ~
or ^
operator then npm will upgrade to you to the latest version that satisfies your semver string.
Actually 1.1.1 is not broccoli version that is node-sass version and I have report bug because it is breaking the broccoli-sass package as well.
The node-sass author has indicated that 1.1.4 could be a fix - have you tried? I'd say we're probably going to be reluctant to push a version that prevents node-sass updates. An alternative is for you to use your own fork of broccoli-sass and specify 1.1.1 in that. Let me know if you want help doing that, it's pretty easy.
node-sass 1.1.4 does not fix the problem.
As a temporary fix I downgraded to broccoli-sass 0.2.4 which uses node-sass 0.9.6. That has 'fixed' the issue for now.
Okay, closing the issue. Feel free to reopen if you like.
Hi We are facing issue with travis build and issue is caused by broccoli-sass as it uses node-sass internally I have reported same bug on node-sass and they asked me to try 1.1.1 version however when we ran travis build again broccoli picked up the 1.1.3 version
https://github.com/sass/node-sass/issues/490
could you please guide ?
Thanks