Repository navigation
v0.3.0
Changes
- feat(playground): ✨ Show telemetry from live requests
Release details
- npm: https://www.npmjs.com/package/@haskou/metrics/v/0.3.0
- Pull request: #2
- Source branch:
- Version bump:
Pull request notes
Changes
- Replace the fixed delay and forced failure controls with a live GitHub repository request.
- Present repository data, metrics, structured logs, and stack traces as readable UI elements.
- Add explicit errors for invalid repository names and unsuccessful GitHub responses.
- Import the Node resource and system clock adapters directly so browser builds do not traverse
prom-client.
Motivation
The previous playground manufactured an 80 ms duration and accepted a boolean that forced the method to fail. Those controls demonstrated the output shape without proving that the library measured real work.
The new flow calls GitHub's public API through GitHubRepositoryFinder.find(). Visitors can inspect a public repository or enter a missing repository to capture a real HTTP failure.
Impact
The playground now reports network duration, calls, failures, logs, and stack traces produced by real executions. It keeps arguments out of telemetry and explains that CPU and RAM sampling require the Node.js adapter.
Direct adapter imports also remove Node module externalization warnings from the browser bundle.
Validation
yarn format:checkyarn lintyarn test:coverage: 39 suites, 81 tests, and 100% coverageyarn test:packageyarn pages:build