Munter / tolk

A file reader that promises to translate non-web assets to web assets given the available transpilers. Autoprefixing, sourcemaps and all!
27 stars 0 forks source link

Update node-sass to version 3.5.1 šŸš€ #141

Closed greenkeeperio-bot closed 8 years ago

greenkeeperio-bot commented 8 years ago

Hello :wave:

:rocket::rocket::rocket:

node-sass just published its new version 3.5.1, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of node-sass ā€“ otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging :palm_tree:


GitHub Release

Deprecation

A previously undocumented process.sass has been deprecated (#1427). It will be removed in a future release. Access this API will produce a deprecation warning in the console.

LibSass 3.3.5

This release includes the recent massive Delorean release as well as couple follow up bug fix release. We delayed this release until LibSass had fixed some issue that cropped in Delorean.

Check the changelogs for more information

Improved installation errors

"The libsass binding was not found.ā€

Say goodbye to this infamous error. The root cause is unavoidable but we can do a better job and helping you fix it without filing an issue. Thanks to @xzyfer you'll now encounter something a bit more friendly!

Node Sass does not yet support your current environment: OS X 64-bit with Node.js 4.x
For more information on which environments are supported please see:
http://....

Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 4.x
Found bindings for the following environments:

  • OS X 64-bit with io.js 3.x
  • OS X 64-bit with Node.js 5.x This usually happens because your environment has changed since running npm install. Run npm rebuild node-sass to build the binding for your current environment.

Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 4.x
This usually happens because your environment has changed since running npm install.
Run npm rebuild node-sass to build the binding for your current environment.

Custom functions

Thanks to @eoneill custom functions now have access to current render context via this.

The benefit of this is that custom functions can persist data (be stateful), for the lifespan of the render. For example this is now possible:

{
  ...,
  functions: {
    "register-foo($foo)": function($foo) {
      this.myNamespace.$foo = $foo;
      ...
    },
    "get-foo()": function() {
      return this.myNamespace.$foo;
    }
  }
}

Features

Fixes

Misc

Thanks!

As always the Node Sass would love to give a huge "thank you!" to all the contributors that made this release possible! We couldn't do it without you. ā¤ļø ā¤ļø ā¤ļø


The new version differs by 94 commits .

There are 94 commits in total. See the full diff.


This pull request was created by greenkeeper.io. It keeps your software up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap:

coveralls commented 8 years ago

Coverage Status

Coverage remained the same at 93.103% when pulling 32548665c8971b20ba9337b4bd619524bafdc8d2 on greenkeeper-node-sass-3.5.1 into b1751e5ced44d06134eb57534258d508ac9d99fa on master.