Misc. Fixes

[am11]

• Build: Use node-gyp from dependencies.
  • Code: Minor refactoring.
• CI: Tests io.js runtime.
  • Promotes node.js to v1.2.
• Test: Adds outFile related tests.
• Test: Adds sourceMap path related tests.

[coveralls]

Coverage increased (+0.18%) to 92.77% when pulling cebf678 on am11:master into fe1d59f on sass:master.

[coveralls]

Coverage increased (+3.79%) to 96.39% when pulling 60031fb on am11:master into fe1d59f on sass:master.

[coveralls]

Coverage increased (+5.0%) to 97.59% when pulling 5a31a68 on am11:master into fe1d59f on sass:master.

[am11]

Coverage!!! ⚡

[austinpray]

@am11 keep going!! 100%%% coverage or go home

[xzyfer]

Can you give some context to what you mean by

Use node-gyp from dependencies

[am11]

@xzyfer, for example I used to run node-gyp rebuild or node scripts/build -f. Both of these use node-gyp installed at global scope (npm install -g node-gyp). Also, node-gyp was not in our package dependency. There are two problems with this:

• only pangyp (a fork of node-gyp) supports io.js at the moment (soon official node-gyp will bring the support as well; there is an open PR).
• people seldom update their global installations.

With this change, all you need to do is to run node scripts/build, node scripts/build --force (or -f) or node scripts/build --debug (or -d). You can use both -f and -d flags (-fd or -df isn't supported though). This will execute (shell out) runtime-aware build command.

[coveralls]

Coverage increased (+6.19%) to 98.78% when pulling b48d5d6 on am11:master into fe1d59f on sass:master.

[am11]

io.js is failing because it is building binary with io.js runtime but npm test job is agnostic of runtime at the moment. That would be a complicated solution to make CIs scripts runtime-aware. Something like: koajs/koa@6d5f506.

Also something has changed in io.js v1.1 (and perhaps corresponding libuv), due to which it is failing some tests locally as well. (was passing all with io.js v1.0.x though).

Nonetheless, we can build io.js 1.1 binaries for node-sass 2.0.0 with pangyp (node scripts/build). 😎

[am11]

@austinpray that is the plan! :)

Just gained a bit more with this diff:

- try { 
-  err = JSON.parse(err); 
- } catch (e) { 
-  err = { message: err }; 
- } 
- 
+ err = JSON.parse(err); 

Note that I removed try-catch because we don't need defensive programming. It is an "interface promise" by LibSass API that the errors shall be returned in JSON format. If there is an anomaly then the bug belongs to LibSass. 🪲

[xzyfer]

Thanks for the clarification @am11. The global node-gyp caught me out recently as well. This is much better.