denoland / denoland/deploy_feedback
Missing Parts of the Performance API? (specifically "clearResourceTimings")
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
I was trying to see if I could get [OpenTelemetry's JS distribution](https://github.com/open-telemetry/opentelemetry-js) (which currently only has Node and Browser support. Here's the [issue for Deno](https://github.com/open-telemetry/opentelemetry-js/issues/2293)) to work in Deno Deploy, and I noticed in the process that the following call to the Web Performance API was error-ing out.
I believe [this](https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/opentelemetry-instrumentation-fetch/src/fetch.ts#L181) is where the call was coming from in code.
```
performance.clearResourceTimings();
```
And this was the error I was seeing (from a reproduction case with only the above line in it
```
TypeError: performance.clearResourceTimings is not a function
```
This[ other issue](https://github.com/denoland/deploy_feedback/issues/14#issuecomment-992078843) led me to the docs for Deno Deploy's support for the Performance API, but all I could find there was a link to MDN.
Part of me is wondering if this was omitted intentionally (maybe relating to the Spectre concerns from [this issue](https://github.com/denoland/deploy_feedback/issues/53)?), but I wasn't sure, so wanted to ask.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the one-line reproduction for performance.clearResourceTimings() and compare it with the Performance API documentation linked in the issue. Read the referenced opentelemetry-instrumentation-fetch/src/fetch.ts call site and the linked Spectre discussion to determine whether the omission is intentional. Done means the support decision is established and the relevant Deploy documentation or behavior is updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, cloud, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100