nan 2.0.1 required due to introduction
of Nan::NewInstance(v8::Local<v8::Function)>, int, v8::Local<v8::Value>)
constructor:

    https://github.com/nodejs/nan/commit/29450ed1670051613ffea9dd3f980f8685feceb4

Use Nan::To<Type> instead of ->ToType() to
convert caller supplied objects in renderXXX
functions.

Verify that provided options, options.result
and options.result.stats are all valid
objects provided by the caller.
Throw TypeException otherwise.

Introduce low-level tests that invoke
C++ function directly, without additional
JavaScript wrappers.

No need to have EscapableHandleScope, since local
handle is not returned by the method - only
assigned to an objects supplied by the caller.

For bool, double, [u]int32_t there is no need to wrap
a returned value in Nan::New()

https://github.com/nodejs/nan/blob/master/doc/methods.md#api_nan_return_value

The code has been updated to meet
the requirements of the updated V8 engine
as provided by io.js.

In some cases additional EscapableHandleScope
has been provided.

SassValueWrapper<T>::New has been changed:
in case of instance construction via
the function call "sass.types.Color(0,0,0)"
instead of "new sass.types.Color(0,0,0)"
the "new" part is no longer executed by
falling through. This should not be necessary
because the constructor is called by
the NewInstance call anyway.

This fixes the following error:

FATAL ERROR: v8::Object::SetAlignedPointerInInternalField() Internal field out of bounds

Remove unused ctx_w

Provide nodeSassConfig hardcoded defaults

Don't launch npm in the PowerShell

Misc. updates

Updates troubleshooting guide.

The issue was fixed by rvagg/pangyp#5 and shipped with pangyp v2.0.

Some private npm repositiories seem not to carry
custom package.json properties around.

Fixes: https://github.com/sass/node-sass/issues/1030

Remove extra ',' in README

There might be issues with running npm under PS,
therefore let's run npm under CMD.

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

http://help.appveyor.com/discussions/problems/2347-npm-275prefer-global-warning-causes-failure-command-executed-with-exception#comment_37223989

https://github.com/npm/npm/issues/8517

Effectively reverts: https://github.com/sass/node-sass/pull/995

Correct typeof reference in README

JavaScript's typeof operator returns "string" not "String" for string values and objects

Change "feth" -> "fetch" in extensions.js comment

Release 3.2.0

Bump Libsass to 3.2.5

Lock to npm@2.7.5 in AppVeyor

We need this in order work around an issue with npm
https://github.com/npm/npm/issues/8517

Release v3.1.2

Fix multi-file compile only writes to the last path when multiple files import a changed partial

CLI: Adds source-map=directory support

* For multi-file compilation.
* Written test.
* Usage:

  ```javascript
  node-sass --source-map source-map/dir --output css/path style/src/
  ```

Issue URL: #903.
PR URL: #964.

Release v3.1.1

Fix ability to watch whole directory