andrew/node-sass — pull request #148 by nschonni (2013-09-04 00:54:13+00:00)
Title: Build: Add v8 specific platform builds

Idea courtesy of node-fibers.
When installing, check to see if there is a compatible binary version for the current version of v8. v8 3.6 = Node 0.6, 3.11 = Node 0.8, 3.14 = Node 0.10. The test suite is run as well, so that any underlying libsass breaks will be rebuilt.

Closes gh-146
___

I added the `console.log('Please consider contributing the release binary to node-sass for npm distribution.');` line, but you'll have to figure out a method for accepting binaries to include (DropBox, etc...). Alternately you could create a `node-sass-binary` repo for accepting PRs.
___
The rebuild is still triggered on Windows due to 3 failing tests in the new cli code.
```
> node-sass@0.6.4 test C:\Workspaces\node-sass
> mocha test

........................

× 3 of 24 tests failed:

1) cli should print help when run with no arguments:
AssertionError: false == true
at C:\Workspaces\node-sass\test\cli.js:31:12
at ChildProcess.exithandler (child_process.js:641:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Process.ChildProcess._handle.onexit (child_process.js:802:5

2) cli should compile sample.scss as sample.css:
AssertionError: false == true
at C:\Workspaces\node-sass\test\cli.js:43:14
at Object.cb [as oncomplete] (fs.js:168:19)

3) cli should compile sample.scss to ../out.css:
AssertionError: false == true
at C:\Workspaces\node-sass\test\cli.js:58:14
at Object.cb [as oncomplete] (fs.js:168:19)

npm ERR! weird error 3
npm ERR! not ok code 0
````