delta/node-new.git/src/node_errors.h, branch try_Python3_on_macOS

crypto: don't expose openssl internals

2019-08-29T04:42:58+00:00

PR-URL: https://github.com/nodejs/node/pull/29325
Reviewed-By: Ujjwal Sharma 
Reviewed-By: James M Snell 
Reviewed-By: Ben Noordhuis 
Reviewed-By: Tobias Nießen

module: exports error as MODULE_NOT_FOUND

2019-08-02T03:36:27+00:00

PR-URL: https://github.com/nodejs/node/pull/28905
Reviewed-By: Rich Trott 
Reviewed-By: Colin Ihrig 
Reviewed-By: Jan Krems 
Reviewed-By: Luigi Pinca 
Reviewed-By: Trivikram Kamat

module: implement "exports" proposal for CommonJS

2019-07-23T23:11:20+00:00

Refs: https://github.com/jkrems/proposal-pkg-exports/issues/36
Refs: https://github.com/nodejs/node/pull/28568

PR-URL: https://github.com/nodejs/node/pull/28759
Reviewed-By: Guy Bedford 
Reviewed-By: Bradley Farias

src: refactor uncaught exception handling

2019-06-19T08:16:37+00:00

The C++ land `node::FatalException()` is not in fact fatal anymore.
It gives the user a chance to handle the uncaught exception
globally by listening to the `uncaughtException` event. This patch
renames it to `TriggerUncaughtException` in C++ to avoid the confusion.

In addition rename the JS land handler to `onGlobalUncaughtException`
to reflect its purpose - we have to keep the alias
`process._fatalException` and use that for now since it has been
monkey-patchable in the user land.

This patch also

- Adds more comments to the global uncaught exception handling routine
- Puts a few other C++ error handling functions into the `errors`
  namespace
- Moves error-handling-related bindings to the `errors` binding.

Refs: https://github.com/nodejs/node/commit/2b252acea47af3ebeac3d7e68277f015667264cc

PR-URL: https://github.com/nodejs/node/pull/28257
Reviewed-By: Anna Henningsen 
Reviewed-By: Benjamin Gruenbaum 
Reviewed-By: Franziska Hinkelmann

worker: make MessagePort constructor non-callable

2019-06-13T03:56:44+00:00

Refactor the C++ code for creating `MessagePort`s to skip calling the
constructor and instead directly instantiating the `InstanceTemplate`,
and always throw an error from the `MessagePort` constructor.

This aligns behaviour with the web, and creating single `MessagePort`s
does not make sense anyway.

PR-URL: https://github.com/nodejs/node/pull/28032
Reviewed-By: Rich Trott 
Reviewed-By: Tiancheng "Timothy" Gu 
Reviewed-By: James M Snell

worker: use DataCloneError for unknown native objects

2019-06-10T13:22:54+00:00

This aligns the behaviour better with the web.

PR-URL: https://github.com/nodejs/node/pull/28025
Reviewed-By: Michaël Zasso 
Reviewed-By: Rich Trott 
Reviewed-By: Joyee Cheung 
Reviewed-By: Colin Ihrig 
Reviewed-By: Tiancheng "Timothy" Gu

src: remove util-inl.h from header files

2019-05-13T20:43:26+00:00

Its intended that *-inl.h header files are only included into the src
files that call the inline methods. Explicitly include it into the files
that need it.

PR-URL: https://github.com/nodejs/node/pull/27631
Reviewed-By: Joyee Cheung 
Reviewed-By: James M Snell 
Reviewed-By: Rich Trott 
Reviewed-By: Colin Ihrig

src: move OnMessage to node_errors.cc

2019-04-26T11:03:14+00:00

Rename the per-isolate message listener to `PerIsolateMessageListener`
and move it to `node_errors.cc` since it's part of the error
handling process. It also creates an external reference so it needs
to be exposed in `node_errors.h` for a snapshot builder to know.

PR-URL: https://github.com/nodejs/node/pull/27304
Reviewed-By: Anna Henningsen

process: add --unhandled-rejections flag

2019-04-15T16:29:07+00:00

This adds a flag to define the default behavior for unhandled
rejections. Three modes exist: `none`, `warn` and `strict`. The first
is going to silence all unhandled rejection warnings. The second
behaves identical to the current default with the excetion that no
deprecation warning will be printed and the last is going to throw
an error for each unhandled rejection, just as regular exceptions do.
It is possible to intercept those with the `uncaughtException` hook
as with all other exceptions as well.

This PR has no influence on the existing `unhandledRejection` hook.
If that is used, it will continue to function as before.

PR-URL: https://github.com/nodejs/node/pull/26599
Reviewed-By: Benjamin Gruenbaum 
Reviewed-By: Matteo Collina 
Reviewed-By: Matheus Marchini 
Reviewed-By: Michael Dawson 
Reviewed-By: Сковорода Никита Андреевич 
Reviewed-By: Sakthipriyan Vairamani

src: print error before aborting

2019-04-15T16:25:05+00:00

In case of fatal errors, first print the error before aborting in
case the process should abort on uncaught exceptions.

PR-URL: https://github.com/nodejs/node/pull/26599
Reviewed-By: Benjamin Gruenbaum 
Reviewed-By: Matteo Collina 
Reviewed-By: Matheus Marchini 
Reviewed-By: Michael Dawson 
Reviewed-By: Сковорода Никита Андреевич 
Reviewed-By: Sakthipriyan Vairamani