evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
Opinionated, caching, retrying fetch client for Node.js with enterprise-grade HTTP features
Agent Success
Agent success rate when using this tile
74%
Improvement
Agent success rate improvement when using this tile compared to baseline
1.68x
Baseline
Agent success rate without this tile
44%
tessl install tessl/npm-make-fetch-happen@15.0.0Generated
Agent Claude Code
Scenario 1
HTTP caching via cachePath with fetch-style cache modes
Scenario 2
Fetch wrapper with Request/Response exports and chainable defaults
Scenario 3
Cache metadata controls including cacheAdditionalHeaders, conditional-request cache bypass, and non-GET invalidation
Scenario 4
Automatic retries with configurable backoff and attempt tracking
Scenario 5
Streaming pipelines that tee responses into cache while buffering integrity/size events for late listeners
Scenario 6
Redirect handling with protocol switches and manual/error modes
Scenario 7
Subresource Integrity verification with ssri-driven integrity/size events and cached hashes
Scenario 8
Stale and offline cache behaviors with revalidation and only-if-cached error surfacing
Scenario 9
Proxy and agent configuration including TLS, DNS cache, and socket pooling