Define best practices for monitoring of single page apps via UT / custom Entries
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Bikeshed
- Stars
- 31
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Continuation of https://github.com/w3c/charter-webperf/issues/27.
As we iterate on L3, we should define the recommended best practices for frameworks and SPA's on how to use User Timing and custom Performance Entries to surface perf data in an interoperable way — e.g. such that various DevTool clients can consume and visualize it, RUM analytics, etc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked charter-webperf issue 27 and the WICG custom Performance Entries proposal. Define recommended practices for frameworks and SPAs using User Timing and custom Performance Entries, with interoperability for DevTools clients and RUM analytics as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100