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

Update node-sass@v3.7.0 #130

Merged
merged 1 commit into from
May 18, 2016
Merged

Update node-sass@v3.7.0 #130

merged 1 commit into from
May 18, 2016

Conversation

xzyfer
Copy link
Contributor

@xzyfer xzyfer commented May 11, 2016

The current locked version, v3.4.2, is very old and no longer supported.
It also does not support Node 6.
This causing many people issues including harp users.

sintaxi/harp#556

The current locked version, v3.4.2, is very old and no longer supported. 
It also does not support Node 6. 
This causing many people issues including harp users.

sintaxi/harp#556
@sintaxi
Copy link
Owner

sintaxi commented May 11, 2016

Thanks for taking a look at this.

@kozie
Copy link

kozie commented May 14, 2016

If this could be merged, that would be nice 🤓
Than i don't have to downgrade my node 👍

@kozie
Copy link

kozie commented May 18, 2016

Sorry to bother again but isn't it just a matter of merging the above PR into your branch to fix the whole Node 6.x issue for terraform and harp?

@sintaxi sintaxi merged commit a6669a6 into sintaxi:master May 18, 2016
@sintaxi
Copy link
Owner

sintaxi commented May 18, 2016

Thanks!

@xzyfer
Copy link
Contributor Author

xzyfer commented May 18, 2016

@sintaxi it's worth giving this article a read as this update my cause users code to start throwing errors if there were previously doing the wrong thing.

https://medium.com/@xzyfer/why-node-sass-broke-your-code-and-semver-1b3e409c57b9#.6jh3adpe0

@xzyfer xzyfer deleted the patch-1 branch May 18, 2016 06:26
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

Successfully merging this pull request may close these issues.

3 participants