npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@anuragdaksh7/net-client

v0.1.0

Published

A framework-agnostic request-state API client built on fetch

Readme

Net Client (Request-State API Client)

A framework-agnostic, fetch-based API client that gives you per-request loading, data, and error state — without React Query, Axios, or magic.

Built out of real pain.


Why this exists

Handling API calls is one of the most repetitive and messy parts of building apps.

Most codebases end up with:

  • global loading flags that break with concurrent requests
  • Axios responses typed as any
  • callbacks everywhere
  • hooks doing transport + state + UI
  • logic that works in React but not on the server

HTTP clients return Promises.
Apps need request state.

This library separates the two.


Core idea

Instead of this:

await fetch(...)

You get this:

request.run()
request.loading
request.data
request.error

Each API call becomes a stateful request controller.


What this library is (and isn’t)

It is

  • fetch-based
  • Bun / Node / Browser compatible
  • framework-agnostic
  • per-request state (loading / data / error)
  • usable in React and server scripts
  • explicit and predictable

It is not

  • a React-only library
  • a caching framework
  • a replacement for React Query
  • Axios with a different name
  • opinionated about UI or toasts

Architecture

HttpClient        → HTTP transport (fetch, headers, errors)
createRequest     → per-request state controller
Your app          → UI / hooks / logs