nodejs / nodejs/node-core-utils
Collect analytics, logs, capture errors
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
Is that something we would be interested in? The tool is only (meant to be) used by collaborators anyway, and capturing some analytics as well as logs and errors could be useful (at least errors, so we know when something breaks).
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
No files, tests, or entry points are named. Start by surveying the node-core-utils CLI and its existing logging and error paths, then clarify which analytics, logs, and errors should be collected. Done requires an agreed scope and collection approach before implementation can be assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100