GoogleChrome / GoogleChrome/web-vitals
Consider creating a DEBUG version of the library
- Dominant language
- JavaScript
- Stars
- 8.6k
- Forks
- 530
- Avg merge
- 3h 4m
- Merged PRs (30d)
- 3
Description
A number of users have requested additional logging to warn users of common issues that may arise (e.g. #138).
I hesitate to increase the size of the production library with logging that most likely will be ignored, but perhaps we could create a debug version of the library users can run in development to help them debug issues.
What do folks think? Would this be useful?
Contributor guide
Research direction
The issue proposes a separate debug version of the library with additional logging, but names no files, tests, or entry points. Start by reviewing the library structure and the related discussion in issue #138, then determine the scope and how a debug build would be produced. Done would mean an agreed design and defined behavior for development-time warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100