v3.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

v3.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

v3.11.0

Features

• Better cache reuse for faster installs (#1566, @nschonni)
• Respect NO_PROXY when downloading the binary (#1724, @xzyfer)
• Add Node 7 support (#1766, @xzyfer)

Fixes

• SASS_BINARY_SITE typo documentation (#1744, @pselden)
• 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

v3.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

v3.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

v3.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

v3.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

v3.8.0

Features

• Add an audible cue when there's a CLI error behind a --error-bell CLI flag (@Peterhactch, #1578)
• Replace cross-spawn-async with cross-spawn (@danez, #1563)
• Let watcher know when files are added or removed (@xzyfer, #1538)
• Add missing jsdoc for public API functions (@nschonni, #1528)
• Add a changelog (@xzyfer, #1523)
• Add Node.js 6 support to readme (@coderbyheart, #1506)

Fixes

• Fix code coverage reporting (@nschonni, #1583)
• Fix the options object passed to render and renderSync being mutated (@xzyfer, #1168)

---

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

v3.7.0

Node.js 6 support

You've asked, and asked, and asked... and here it is. It took a little longer than we'd hoped due a bug we discovered in Node.js 6 which broken our Windows builds.

Previous versions of Node Sass worked fine with Node.js 6 but produced scary looking warnings the console.

• Work around Node.js 6 bug in Windows CI (@saper, #1514)
• Remove scary Node.js 6 console warnings (@xzyfer, #1484)
• Update NAN to at least 2.3.2 (@xzyfer, #1496)

Update proxy support

Currently to detect user local settings, when downloading the precompiled binaries, we use a deprecated package. We've replaced this packaged with the offical npm environment variables. This drastically simplifies our install script.

Big thanks to @delitescere! (#1333)

Fixes

• Drastically simply we switch Node versions in Travis (@xzyfer, #1500)
• Better error message when installing on an unsupported environments (@nschonni @xzyfer, #1487 #1491)
• Update TODO URL in install error (@nschonni, #1488)
• Add Node.js 6 to CI (@nschonni, #1486)

---

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

v3.6.0

LibSass

We've bumped LibSass to 3.3.6 Herbie

Fixes

• Segfualt when used with materialize-css (#1464)

---

Support Environments

OS	Node
Windows x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5
OSX x64	0.10, 0.12, 1, 2, 3, 4, 5, 6
Linux x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6
FreeBSD x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5

*Linux support refers to Ubuntu, Debian, and CentOS 5