This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of node-sass.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
In v3.12.x we made some change to how did logging. Namely we adopted npmlog, which is used by npm itself. This has caused a variety off issues we have not been able to reliably address. As such v3.13.0 undoes this change. Thanks too all the patient folks who helps up debug our logging issues.
Fixes
Use console.log and console.error for logging (@xzyfer)
Supported Environments
OS
Architecture
Node
Windows
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6,7
OSX
x64
0.10, 0.12, 1, 2, 3, 4, 5, 6, 7
Linux
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6, 7
FreeBSD
i386 & amd64
0.10, 0.12, 1, 2, 3, 4, 5, 6
*Linux support refers to Ubuntu, Debian, and CentOS 5
Hello lovely humans,
node-sass just published its new version 3.13.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of node-sass. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
In v3.12.x we made some change to how did logging. Namely we adopted
npmlog, which is used by npm itself. This has caused a variety off issues we have not been able to reliably address. As such v3.13.0 undoes this change. Thanks too all the patient folks who helps up debug our logging issues.Fixes
console.logandconsole.errorfor logging (@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
The new version differs by 125 commits .
2e7f3703.13.0cb8774fMerge pull request #1806 from sass/feat/console-logd83ebc8Use console for logging instead of npmlog79237e63.12.516b75d5Revert "Send npmlog to stdout"c77632fRevert "Always log to stdout"3aadc7d3.12.4fa4515dAlways log to stdoutbee91ae3.12.3c5a2d38Merge pull request #1803 from sass/feat/log-to-stdoute7ad0cbSend npmlog to stdoute0aef95Fix typo in error handling33fbd2b3.12.259beffcHandle access error when writing binary to cacheaa76f8f3.12.1There are 125 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade