Add nodejs data for PerformanceResourceTiming
#25010
Open
+214
−0
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.
Summary
most are taken from documentation:
https://nodejs.org/docs/latest/api/globals.html#performanceresourcetiming
https://nodejs.org/docs/latest/api/perf_hooks.html#class-performanceresourcetiming
but, note that
initiatorType
,nextHopProtocol
,responseStart
,deliveryType
andresponseStatus
does not has its documentation, thus can not determine its version number via documentation (docs issue fired at nodejs/node#55793)most are implemented via nodejs/node#42725, in https://nodejs.org/zh-cn/blog/release/v16.17.0 and https://nodejs.org/zh-cn/blog/release/v18.2.0; also confirmed
nextHopProtocol
andresponseStart
is implemented here (hereinitiatorType
may return fromtoJSON()
method, but can not access directly)initiatorType
is implemented via nodejs/node#43593, in https://nodejs.org/zh-cn/blog/release/v16.17.0 and https://nodejs.org/zh-cn/blog/release/v18.6.0deliveryType
andresponseStatus
is implemented via nodejs/node#51589, in https://nodejs.org/zh-cn/blog/release/v22.2.0Test results and supporting details
Related issues