N-API offers a way to "wrap" C++ classes and instances so that the class

constructor and methods can be called from JavaScript.

1. The [`napi_define_class`][] API defines a JavaScript class with constructor,

static properties and methods, and instance properties and methods that

correspond to the C++ class.

2. When JavaScript code invokes the constructor, the constructor callback

uses [`napi_wrap`][] to wrap a new C++ instance in a JavaScript object,

then returns the wrapper object.

3. When JavaScript code invokes a method or property accessor on the class,

the corresponding `napi_callback` C++ function is invoked. For an instance

callback, [`napi_unwrap`][] obtains the C++ instance that is the target of

the call.

- Move node.dns into module "dns"

- Move node.fs into module "posix"

- process is no longer the global object. GLOBAL is.

For more information on the API changes see:

http://thread.gmane.org/gmane.comp.lang.javascript.nodejs/6

http://thread.gmane.org/gmane.comp.lang.javascript.nodejs/14

* **v8**: backport fb4ccae from v8 upstream (Vladimir Krivosheev) #4231

- breakout events from v8 to offer better support for external debuggers

* **zlib**: add support for concatenated members (Kári Tristan Helgason)

* Previously, if multiple members were in the same archive, only the first would be read. The others are no longer thrown away.

* **build**:

- Disable V8 snapshots - The hashseed embedded in the snapshot is

currently the same for all runs of the binary. This opens node up to

collision attacks which could result in a Denial of Service. We have

temporarily disabled snapshots until a more robust solution is found

(Ali Ijaz Sheikh)

* **deps**:

- CVE-2017-1000381 - The c-ares function ares_parse_naptr_reply(),

which is used for parsing NAPTR responses, could be triggered to

read memory outside of the given input buffer if the passed in DNS

response packet was crafted in a particular way. This patch checks that

there is enough data for the required elements of an NAPTR record (2

int16, 3 bytes for string lengths) before processing a record. (David

Drysdale)

* **buffer**:

- Reverted the runtime deprecation of calling `Buffer()` without `new`. (Anna Henningsen) [#9529](https://github.com/nodejs/node/pull/9529)

- Fixed `buffer.transcode()` for single-byte character

encodings to `UCS2`. (Anna Henningsen) [#9838](https://github.com/nodejs/node/pull/9838)

* **promise**: `--trace-warnings` now produces useful stacktraces for Promise warnings. (Anna Henningsen) [#9525](https://github.com/nodejs/node/pull/9525)

* **repl**: Fixed a bug preventing correct parsing of generator functions. (Teddy Katz) [#9852](https://github.com/nodejs/node/pull/9852)

* **V8**: Fixed a significant `instanceof` performance regression. (Franziska Hinkelmann) [#9730](https://github.com/nodejs/node/pull/9730)

3. Wrap all other lines at 72 columns (except for long URLs).

4. If your patch fixes an open issue, you can add a reference to it at the end

of the log. Use the `Fixes:` prefix and the full issue URL. For other

references use `Refs:`.

Examples:

- `Fixes: https://github.com/nodejs/node/issues/1337`