delta/node-new.git/src/node_options.cc, branch pull-request-doc-updates

process: move DEP0062 (node --debug) to end-of-life

2019-02-01T21:45:05+00:00

This has already been practically end-of-life since `node --debug`
alone would exit the process. This patch drops support of
`node --inspect --debug-brk` as well.

`node --inspect --debug-brk` has been deprecated since v8,
it has been maintained so that vendors can target Node.js
v6 and above without detecting versions.
The support of `--inspect`, which starts from v6, will reach
end-of-life in April 2019, it should be safe to drop the support
of `--inspect --debug-brk` altogether in v12.

Also removes `process._deprecatedDebugBrk`

PR-URL: https://github.com/nodejs/node/pull/25828
Refs: https://github.com/nodejs/node/pull/12949
Reviewed-By: Anna Henningsen 
Reviewed-By: Eugene Ostroukhov 
Reviewed-By: Richard Lau 
Reviewed-By: Matteo Collina

process: exit on --debug and --debug-brk after option parsing

2019-02-01T21:45:05+00:00

Moves the exit of `--debug` and `--debug-brk` earlier, that is,
after the option parsing is done in the C++ land.

Also removes `process._invalidDebug`.

PR-URL: https://github.com/nodejs/node/pull/25828
Refs: https://github.com/nodejs/node/pull/12949
Reviewed-By: Anna Henningsen 
Reviewed-By: Eugene Ostroukhov 
Reviewed-By: Richard Lau 
Reviewed-By: Matteo Collina

src: workaround MSVC compiler bug

2019-01-31T23:47:08+00:00

PR-URL: https://github.com/nodejs/node/pull/25596
Fixes: https://github.com/nodejs/node/issues/25593
Refs: https://developercommunity.visualstudio.com/content/problem/432157/dynamic-initializers-out-of-order.html
Reviewed-By: Bartosz Sosnowski 
Reviewed-By: Anna Henningsen

src: simplify inspector initialization in node::Start()

2019-01-27T20:40:24+00:00

Remove the `StartInspector` and `InspectorStarted` abstraction
out of `v8_platform`, and error out early and directly in the
option parser if Node is configured with NODE_USE_V8_PLATFORM and
inspector enabled but the user still tries to use inspector options.

PR-URL: https://github.com/nodejs/node/pull/25612
Reviewed-By: Anna Henningsen 
Reviewed-By: Ben Noordhuis 
Reviewed-By: Colin Ihrig

src: remove has_experimental_policy option

2019-01-25T06:36:49+00:00

This would be set when `--experimental-policy` was set,
but since an empty string does not refer to a valid file,
we can just check the value of `--experimental-policy`
directly.

PR-URL: https://github.com/nodejs/node/pull/25628
Reviewed-By: Colin Ihrig 
Reviewed-By: Daniel Bevenius 
Reviewed-By: Gus Caplan 
Reviewed-By: Sakthipriyan Vairamani 
Reviewed-By: Minwoo Jung

report: simplify option checking

2019-01-22T22:58:51+00:00

Also update the code for house style.

PR-URL: https://github.com/nodejs/node/pull/25597
Reviewed-By: Anna Henningsen 
Reviewed-By: Refael Ackermann 
Reviewed-By: Denys Otrishko

src: reduce includes of node_internals.h

2019-01-21T06:54:42+00:00

PR-URL: https://github.com/nodejs/node/pull/25507
Reviewed-By: Daniel Bevenius 
Reviewed-By: Ben Noordhuis 
Reviewed-By: Colin Ihrig 
Reviewed-By: Anna Henningsen 
Reviewed-By: James M Snell

src: merge into core

2019-01-18T05:04:04+00:00

Make node-report part of core runtime because:

1. When enabled, node-report significantly helps root cause various
types of problems, including support issues sent to the various repos
of the Node.js organization.

2. The requirement of explicitly adding the dependency to node-report
in user applications often represents a blocker to adoption.

Major deviation from the module version of the node-report is that the
report is generated in JSON format, as opposed to human readable text.

No new functionalities have been added, changes that are required for
melding it as a built-in capability has been affected on the module
version of node-report (https://github.com/nodejs/node-report)

Co-authored-by: Bidisha Pyne 
Co-authored-by: Howard Hellyer 
Co-authored-by: Jeremiah Senkpiel 
Co-authored-by: Julian Alimin 
Co-authored-by: Lakshmi Swetha Gopireddy 
Co-authored-by: Manusaporn Treerungroj 
Co-authored-by: Michael Dawson 
Co-authored-by: Richard Chamberlain 
Co-authored-by: Richard Lau 
Co-authored-by: Sam Roberts 
Co-authored-by: Vipin Menon 

PR-URL: https://github.com/nodejs/node/pull/22712
Reviewed-By: Anna Henningsen 
Reviewed-By: James M Snell 
Reviewed-By: Michael Dawson 
Reviewed-By: Vse Mozhet Byt

policy: manifest with subresource integrity checks

2019-01-17T15:43:42+00:00

This enables code loaded via the module system to be checked for
integrity to ensure the code loaded matches expectations.

PR-URL: https://github.com/nodejs/node/pull/23834
Reviewed-By: Guy Bedford 
Reviewed-By: Vladimir de Turckheim 
Reviewed-By: Matteo Collina

worker: remove `--experimental-worker` flag

2019-01-08T23:31:33+00:00

Having an experimental feature behind a flag makes change
if we are expecting significant breaking changes to its API.

Since the Worker API has been essentially stable since
its initial introduction, and no noticeable doubt about
possibly not keeping the feature around has been voiced,
removing the flag and thereby reducing the barrier to experimentation,
and consequently receiving feedback on the implementation,
seems like a good idea.

PR-URL: https://github.com/nodejs/node/pull/25361
Reviewed-By: Rich Trott 
Reviewed-By: Yuta Hiroto 
Reviewed-By: Shingo Inoue 
Reviewed-By: James M Snell 
Reviewed-By: Colin Ihrig 
Reviewed-By: Benjamin Gruenbaum 
Reviewed-By: Tiancheng "Timothy" Gu 
Reviewed-By: Tobias Nießen 
Reviewed-By: Masashi Hirano 
Reviewed-By: Weijia Wang 
Reviewed-By: Gireesh Punathil 
Reviewed-By: Michael Dawson