inspector: allow opt-out of console.* hijacking

[mscdex]

• Version: all
• Platform: n/a
• Subsystem: inspector

It would be nice to be able to opt out of console.* "hijacking" by the inspector integration for situations where stdout (and/or stderr) is redirected to a file and the process produces a lot of output. Not only is the output duplicated (once in the file and again in the browser), but it can eat up extra memory if you don't need/care to see the console output in the browser.

[eugeneo]

It is up to debugger front-end to enable/disable Console agent...

Now that we almost have inspector module in Node (#12263) we can start expanding the API. E.g. we can introduce "disableConsoleWatcher", "clearConsoleHistory". Any other suggestions?

[mscdex]

For my request, I was thinking the opt-out option would just avoid calling installInspectorConsole() in lib/internal/bootstrap_node.js. This would probably be a command-line flag or similar, but I guess it could technically be toggleable during runtime as well by uninstalling/reinstalling the inspector hook?

[Trott]

Should this remain open? (Seems like it, but maybe something happened in the last three months or maybe it's not a desirable feature for a reason that needs to be documented here or...)

[refack]

Put into https://github.com/nodejs/node/projects/13 backlog