A new version was just released of node-sass, so Doppins
has upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging! :shipit:
Upgraded node-sass from ~3.8.0 to ~4.5.0
Changelog:
Version 4.5.0
Features
Build Windows binaries with Visual Studio 2015 for Node 6+ (@am11@xzyfer, #1854)
Fixes
Fix includePaths no longer containing cwd by default (@xzyfer, #1876)
Fix slow down in watcher responsiveness (@xzyfer, #1869)
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
Alpine
x64
4, 6, 7
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.4.0
LibSass
LibSass has been bumped from 3.4.3 to 3.5.0.beta.2. This update brings some more performance improvements and support for CSS Grid Syntax. Check the LibSass changelogs for more information.
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.3.0
Significant internal changes for CITGM support.
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
Alpine
x64
4, 6, 7
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.2.0
LibSass to 3.4.3
LibSass has been bumped from 3.4.0 to 3.4.3. This update brings significant memory usage improvements. Check the LibSass changelogs for more information.
Stack depth counter leaking between processes (#1669)
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
Alpine
x64
4, 6, 7
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.1.1
Fixes
Lock sass-spec dependency to v3.4.0 (@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
Alpine
x64
4, 6, 7
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.1.0
Alpine Linux support
The Linux binaries we supply are not compatible with the way Node is compiled on Alpine Linux. This means that although the installation will succeed, it takes much longer because the native code needs to be compiled locally.
Thanks to the hard work of @lox and @S-YOU we're now able to supply Alpine Linux compatible binaries.
Read more about what was involved in #1589.
Fixes
Replace lodash.isarray with Array.isArray (@daltones, #1829)
CLI prematurely exiting before the output stream is fully flushed (@ysugimoto, #1823)
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
Alpine
x64
4, 6, 7
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.0.0
This release is backwards compatible with v3.13.1 in case you encounter issues with the latest LibSass.
LibSass 3.4.0
Check out the LibSass release notes (https://github.com/sass/libsass/releases/tag/3.4.0) for more information.
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
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.13.1
Fixes
Removed top-level return statement from cli (@bfred-it, #1826)
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.14.0-0
LibSass 3.4.0-RC1
Checkout the LibSass changelog (https://github.com/sass/libsass/releases/tag/3.4.0-RC1).
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
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.13.0
In v3.12.x we made some change to how we 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
Version 3.12.5
Fixes
More fixes to logging
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
Version 3.12.4
Fixes
Always log to stdout (@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
Version 3.12.3
Fixes
Log to stdout instead of stderr (@xzyfer, #1801)
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
Version 3.12.2
Fixes
Better handle fs error when during install (@xzyfer, #1799)
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
Version 3.12.1
Fixes
Better handle fs error when during install (@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
Version 3.12.0
Features
More reliable watcher (@marvinhagemeister, #1731)
Improved installation logging (@xzyfer, #1796)
Binary caching for faster installs (@nschonni, #1714@xzyfer#1782)
Fixes
Stop leaking state in tests (@marvinhagemeister, #1748#1798)
Respect --no-progress npm flag (@xzyfer)
Correct typos in installation 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
Version 3.11.3
Fixes
Replace leftover console.logs with npmlog (@mcdado, #1786)
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
Version 3.11.2
Fixes
Regressions in handling proxies (@xzyfer, #1785, #1787)
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
Version 3.11.1
Fixes
Revert install caching (@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
Version 3.11.0
Features
Better cache reuse for faster installs (#1566, @nschonni)
Respect NO_PROXY when downloading the binary (#1724, @xzyfer)
Fix links in troubleshooting documentation (#1753, @NicolaiSoeborg)
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
Version 3.10.1
Fixes
This release address a couple minor bugs affecting the node-sass integration into the node-citgm.
Make the missing binding error message test more fault tolerant (@xzyfer)
Publish test to npm
Supported Environments
OS
Architecture
Node
Windows
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
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
Version 3.10.0
Sass Spec
In v3.9.0 started publishing our test suite to npm. This caused issues for users on systems with poor unicode support or file path length limits. This changed was reverted until we could engineer a better solution.
In this release we've migrated our test suite to a separate npm module which is now a devDependency. With change users will only download the test suite on an opt-in basis by explicitly install devDependencies.
@nschonni, @xzyfer, #1686
Misc
Update ISSUE_TEMPLATE (@nschonni, #1717)
Replace util._extend with lodash.assign (@nschonni, #1711)
Bump ESLint to v3 (@nschonni, #1700)
Supported Environments
OS
Architecture
Node
Windows
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
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
Version 3.9.3
Fix filename issues š
In v3.9.0 we began publishing our test suite to npm as part of our release. We did this be compliant with the node-citgm project. Being the citgm would give us early warning of changes in Node that would break Node Sass for users. We'd hoped this would allows to address these issue early and avoid the dozens of bug reports we receive.
However some users have experience issues with some test filenames include unicode characters. Some npm@2 users have also experienced issues with our path names being too long.
As a result we're temporarily reverting the addition of our test suite until we have a solution for these issues.
We're sorry š
Noone ever wants to break someone's build. We had expected this minor change to be innocuous.
Unfortunately we had not accounted for the variety of operating environments our +2M monthly downloads would be running on. Although the number of affected users was small, the failure was at times catastrophic.
Having this feature is important to us, but not breaking your builds, and workflows is critical.
Supported Environments
OS
Architecture
Node
Windows
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
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
Version 3.9.0
Installation improvements
Installation issues are a steady background noise of Node Sass. These issues are mostly to local environment issues that are simply out of control. These issue take up a lot of time so we've been trying to provide more useful output when an installation fails.
This release we focused on adding more visibility to the binary download process. NPM will now output when it begins to download the binary, where it's downloading the binary from, as well as progress bar. It's how hope that this additional transparency will allow users to self-diagnose local problems before opening an issue.
The download progress bar respects npm's progress config flag.
We've also added a generous download timeout to prevent rare instances of installs hanging infinitely.
@andyxxsd@xzyfer, #1695#1694#1691
CI stability
Our CI has been growing increasingly flakey. After a lot of investigation the main culprit appears to child_process.spawnSync on Node 0.10.x. We've put some work arounds in place to increase the stability of our CI whilst maintaining test coverage.
@nschonni@xzyfer, #1692#1697
SASS_PATH support
You can now set the SASS_PATH environment variable to a colon delimited list of directories and Sass will automatically look in each of them when finding a file for @import. This is a little known feature of Ruby Sass which has been added to aid compatibility.
@nottrobin, #1680
Misc
Update troubleshooting guide with sample output (@xzyfer, #1696)
Publish test to npm (@xzyfer, #1688)
Update troubleshooting guide with instructions to check COMSPEC on Windows (@saper, 1673)
Fix build errors with Electron (@saper, #1631)
Fix issue with libsass_ext in node-gyp (@saper, #1599)
Update CLI usage documentation for clarity (@howlowck, #1593)
Update troubleshooting guide with simplified debugging steps (@mohuk , #1586)
Convert JSHint to ESLint (@nschonni, #1545)
Add an Issue template (@nschonni, #1399)
Replace gitter badge with Slack (@xzyfer)
Supported Environments
OS
Architecture
Node
Windows
x86 & x64
0.10, 0.12, 1, 2, 3, 4, 5, 6
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
Hi!
A new version was just released of
node-sass, so Doppins has upgraded your project's dependency ranges.Make sure that it doesn't break anything, and happy merging! :shipit:
Upgraded node-sass from
~3.8.0to~4.5.0Changelog:
Version 4.5.0
Features
@am11@xzyfer,#1854)Fixes
includePathsno longer containingcwdby default (@xzyfer,#1876)@xzyfer,#1869)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.4.0
LibSass
LibSass has been bumped from 3.4.3 to 3.5.0.beta.2. This update brings some more performance improvements and support for CSS Grid Syntax. Check the LibSass changelogs for more information.
https://github.com/sass/libsass/releases/tag/3.5.0.beta.1)https://github.com/sass/libsass/releases/tag/3.5.0.beta.2)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.3.0
Significant internal changes for CITGM support.
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.2.0
LibSass to 3.4.3
LibSass has been bumped from 3.4.0 to 3.4.3. This update brings significant memory usage improvements. Check the LibSass changelogs for more information.
https://github.com/sass/libsass/releases/tag/3.4.1)https://github.com/sass/libsass/releases/tag/3.4.2)https://github.com/sass/libsass/releases/tag/3.4.3)Fixes
#1669)#1669)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.1.1
Fixes
@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.1.0
Alpine Linux support
The Linux binaries we supply are not compatible with the way Node is compiled on Alpine Linux. This means that although the installation will succeed, it takes much longer because the native code needs to be compiled locally.
Thanks to the hard work of
@loxand@S-YOUwe're now able to supply Alpine Linux compatible binaries.Read more about what was involved in
#1589.Fixes
lodash.isarraywithArray.isArray(@daltones,#1829)@ysugimoto,#1823)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 4.0.0
This release is backwards compatible with v3.13.1 in case you encounter issues with the latest LibSass.
LibSass 3.4.0
Check out the LibSass release notes (
https://github.com/sass/libsass/releases/tag/3.4.0) for more information.Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.13.1
Fixes
@bfred-it,#1826)@tnguyen14,#1824)@xzyfer)sourceCommentsdocumentation (@screamingmunch,#1820)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.14.0-0
LibSass 3.4.0-RC1
Checkout the LibSass changelog (
https://github.com/sass/libsass/releases/tag/3.4.0-RC1).Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.13.0
In v3.12.x we made some change to how we 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
Version 3.12.5
Fixes
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.12.4
Fixes
@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.12.3
Fixes
@xzyfer,#1801)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.12.2
Fixes
@xzyfer,#1799)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.12.1
Fixes
@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.12.0
Features
@marvinhagemeister,#1731)@xzyfer,#1796)@nschonni,#1714@xzyfer#1782)Fixes
@marvinhagemeister,#1748#1798)--no-progressnpm flag (@xzyfer)@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.11.3
Fixes
console.logs withnpmlog(@mcdado,#1786)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.11.2
Fixes
@xzyfer,#1785,#1787)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.11.1
Fixes
@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.11.0
Features
#1566,@nschonni)#1724,@xzyfer)#1766,@xzyfer)Fixes
SASS_BINARY_SITEtypo documentation (#1744,@pselden)#1753,@NicolaiSoeborg)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.10.1
Fixes
This release address a couple minor bugs affecting the node-sass integration into the node-citgm.
@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.10.0
Sass Spec
In v3.9.0 started publishing our test suite to npm. This caused issues for users on systems with poor unicode support or file path length limits. This changed was reverted until we could engineer a better solution.
In this release we've migrated our test suite to a separate npm module which is now a devDependency. With change users will only download the test suite on an opt-in basis by explicitly install devDependencies.
@nschonni,@xzyfer,#1686Misc
@nschonni,#1717)@nschonni,#1711)@nschonni,#1700)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.9.3
Fix filename issues š
In v3.9.0 we began publishing our test suite to npm as part of our release. We did this be compliant with the node-citgm project. Being the citgm would give us early warning of changes in Node that would break Node Sass for users. We'd hoped this would allows to address these issue early and avoid the dozens of bug reports we receive.
However some users have experience issues with some test filenames include unicode characters. Some npm@2 users have also experienced issues with our path names being too long.
As a result we're temporarily reverting the addition of our test suite until we have a solution for these issues.
We're sorry š
Noone ever wants to break someone's build. We had expected this minor change to be innocuous.
Unfortunately we had not accounted for the variety of operating environments our +2M monthly downloads would be running on. Although the number of affected users was small, the failure was at times catastrophic.
Having this feature is important to us, but not breaking your builds, and workflows is critical.
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
Version 3.9.0
Installation improvements
Installation issues are a steady background noise of Node Sass. These issues are mostly to local environment issues that are simply out of control. These issue take up a lot of time so we've been trying to provide more useful output when an installation fails.
This release we focused on adding more visibility to the binary download process. NPM will now output when it begins to download the binary, where it's downloading the binary from, as well as progress bar. It's how hope that this additional transparency will allow users to self-diagnose local problems before opening an issue.
The download progress bar respects npm's
progressconfig flag.We've also added a generous download timeout to prevent rare instances of installs hanging infinitely.
@andyxxsd@xzyfer,#1695#1694#1691CI stability
Our CI has been growing increasingly flakey. After a lot of investigation the main culprit appears to
child_process.spawnSyncon Node 0.10.x. We've put some work arounds in place to increase the stability of our CI whilst maintaining test coverage.@nschonni@xzyfer,#1692#1697SASS_PATH support
You can now set the
SASS_PATHenvironment variable to a colon delimited list of directories and Sass will automatically look in each of them when finding a file for@import. This is a little known feature of Ruby Sass which has been added to aid compatibility.@nottrobin,#1680Misc
@xzyfer,#1696)@xzyfer,#1688)COMSPECon Windows (@saper, 1673)@saper,#1631)libsass_extin node-gyp (@saper,#1599)@howlowck,#1593)@mohuk,#1586)@nschonni,#1545)@nschonni,#1399)@xzyfer)Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5