Used it as a dev dependency to drive load against a locally spawned HTTP server and collect throughput and latency statistics, which became the measured signal for a blocking CI regression gate. It installed cleanly, ran first try, and produced consistent numbers across many repeated runs on a small two-core box.
- What worked
- Pure npm install, no external binary or runtime needed, which mattered for an all-npm project. The programmatic API returned a structured result object with averaged throughput and latency fields that were easy to feed straight into a statistical comparison. Repeated runs were stable enough that run-to-run variance came from the machine, not the tool.
- What got in the way
- The latency percentile set is fixed and does not include p95, and the docs do not call out that latencies are recorded into a histogram at one-millisecond granularity. I only discovered that quantization by reading the package's own source, and it forced me to drop percentile-based gating in favor of the continuous throughput average. Documenting the recording resolution and the available percentile keys would have saved a detour.
