Fix a typo "repsonse" to "response".

Add --follow option to the CLI

Use sass binary url from .npmrc if available

For pull requests and pushes to master just build 32-bit binaries
and do not store artifacts.

Whenever a tag is pushed to the "release" branch - produce
full set of 32-bit and 64-bit binaries, create a GitHub
release (if does not exist already) and attach the binaries
to the release.

Issue open:

http://bit.ly/twoBuilds

 AppVeyor starts two builds in response to the "new commit"
 and "new tag" events.

Import libsass 3.3 code

- New source layout
- New header names for #include
- No need for exception handling in pure C code

Sometimes they generate double notification
on change:

      1) cli node-sass in.scss should watch the full scss dep tree for a single file (scss):

      Uncaught AssertionError: 'body{background:blue}\n\nbody{background:blue}' == 'body{background:blue}'
      + expected - actual

      -body{background:blue}
      -
       body{background:blue}

      at Socket.<anonymous> (test/cli.js:317:16)
      at readableAddChunk (_stream_readable.js:146:16)
      at Socket.Readable.push (_stream_readable.js:110:10)
      at Pipe.onread (net.js:523:20)

https://github.com/sass/node-sass/issues/1152

Fix race conditons in watcher tests

We are getting test failures:

1) cli node-sass in.scss should watch the full scss dep tree for a single file:

      Uncaught AssertionError: false == true

      + expected - actual

      -false

      +true

      at Socket.<anonymous> (test/cli.js:317:9)
      at readableAddChunk (_stream_readable.js:146:16)
      at Socket.Readable.push (_stream_readable.js:110:10)
      at Pipe.onread (net.js:523:20)

Use two different directories for
directory watching CLI tests to
avoid races.

Provide a useful error message when the binding is not found

Currently we show the unhelpful for `libsass` binding not found.
This accounts for a number of reoccurring GitHub issues.
It's also the second largest driver of Google traffic to the
node-sass GitHub repo.

Windows delay hook feature is only needed
on the main module, linked into the shared
library. Don't compile and include
it second time in the bundled libsass.

Related: https://github.com/nodejs/node-gyp/issues/732

Run OSX builds in Travis CI

Now that io.js and Node.js have converged these comments make no
sense.

Add Node.js 4 to AppVeyor

Replace pangyp with node-gyp

We originally adopted pangyp as a tempory work around for iojs
support. This and more has been added to node-gyp and as such
pangyp has been deprecated.

Fix crash in List::SetValue() etc. when trying
to add a bare JavaScript object.

Check for bare objects in lists and maps in test.

Don't use C++ exceptions in the binding code.

Make Travis CI to report failures on Node.js 4.0

In the unlikely event libsass gives us the
value we don't understand use V8 exception
to report failure and exit before calling
a user-defined custom function.

XXX We do not have currently any way
    to test this (that would require mocking
    libsass).

::construct() methods may return NULL and
indicate an error in the returned error value.

This method uses Sass error value
as a vehicle to report the error message,
but returns NULL to indicate constructor
failure.

This is used to tell successful creation
of the Sass error object from the constructor
failure, where no valid Sass object can be
created.