Update node-sass to a 3.0.0 beta.

Especially to not have to deal with sass/node-sass#698, but might contain other fixes to importers, too. Let's see and revert if there's bork.

Author: jareware

node-sass.js

@@ -2,7 +2,6 @@ var fs = require('fs');
 var path = require('path');
 
 // @see https://www.npmjs.com/package/node-sass#importer-v2-0-0-experimental
-// @see https://github.com/sass/node-sass/issues/671 (random console.log(), which is why can't really use --stdout)
 module.exports = function(url, prev, done) {
   var expectedExtension = path.extname(url) === '' ? path.extname(prev) : ''; // if the import had an extension (e.g. ".scss"), use that; if not, use the extension of the importing file
   var next = path.join(path.dirname(prev), url + expectedExtension); // construct import path relative to current file // TODO: Solve https://github.com/sass/node-sass/issues/762

package.json

@@ -9,7 +9,7 @@
     "browserify": "9.0.8",
     "classnames": "1.2.1",
     "mocha": "2.2.4",
-    "node-sass": "2.1.1",
+    "node-sass": "3.0.0-beta.7",
     "react": "0.13.2",
     "reactify": "1.1.0"
   },

test/cases/node-sass/.gitignore

@@ -1,5 +1,5 @@
 {
   "scripts": {
-    "test": "node-sass --importer=$(pwd)/node_modules/component-css-ns/node-sass.js entrypoint.scss > /dev/null 2>&1 && cat entrypoint.css"
+    "test": "cat entrypoint.scss | node-sass --importer=$(pwd)/node_modules/component-css-ns/node-sass"
   }
 }