Node.js 18.8.0 supported Performance interface

[skyclouds2001]

Summary

the exact version of when the Performance class is exposed to global is not mentioned (only mentioned the performance global property)

in node v19.0.0, while other performance related features has been exposed via nodejs/node#44483, the Performance interface has been exposed yet;
in node v16.0.0, only performance global proeprty is exposed to global via nodejs/node#37970;
in node v18.8.0, here the Performance interface is exposed to global via nodejs/node#44220, before this version, it is only available as an internal instance.

Test results and supporting details

https://nodejs.org/docs/latest/api/globals.html#performance
https://nodejs.org/docs/latest/api/perf_hooks.html#perf_hooksperformance

Related issues

[caugner]

How could users interact with this interface, if it wasn't exported prior to 18.8.0?

[skyclouds2001]

though the interface can't be accessed directly, but it can be accessed via performance property: require('perf_hooks').performance.__proto__.constructor

performance.__proto__.constructor === Performance will report true in latest node

and another reason is that there is a rule which force parent feature' version must not be greater or equal than child feature's version

see also #25001 (comment) and #24998 (comment)

[caugner]

it can be accessed via performance property: require('perf_hooks').performance.__proto__.constructor

Should we mention this explicitly? I feel like the previous note was somewhat more informative.

Suggested change

	"notes": "Only available as an internal instance."
	"notes": "Only available as an internal instance (`require('perf_hooks').performance.__proto__.constructor`)."

[caugner]

@skyclouds2001 What do you think about this suggestion? 👆

[skyclouds2001]

I think the info of how to access the interface is not required, as in most case user will not access this interface directly but use its properites and methods; and since the info is only for old node.js version, very fewer user will use it.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[caugner]

LGTM, thanks!