feat: Add support for Node’s [util.inspect.custom]
symbol method
#165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, web browsers display web platform objects in the DevTools console in a nice‑ish way:
Trying the same in JSDOM results in the rather unhelpful:
Long
<pre>
blockWith
runScripts
enabled,Window
becomes even worse:Very long
<pre>
blockNode provides the
util.inspect.custom
symbol, which is registered globally usingSymbol.for("nodejs.util.inspect.custom")
since Node v10, and which can be used to add functions to customise how objects are displayed by the console.Merging this makes it possible for JSDOM and other WebIDL2JS consumers to customise how the Node console and
util.inspect
function displays WebIDL2JS objects.