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

use-health-check

v1.0.0

Published

A React hook for polling an endpoint to check whether it's healthy/reachable.

Readme

use-health-check

A React hook that polls an endpoint to check whether it's healthy/reachable.

Installation

npm install use-health-check

Usage

import { useHealthCheck } from 'use-health-check';

const ApiStatus = () => {
  const { isHealthy, isChecking, lastChecked, responseTime, error, healthCheck } = useHealthCheck(
    'https://api.example.com/health',
    { interval: 30000, timeout: 5000 }
  );

  if (isHealthy === null) return <p>Checking…</p>;

  return (
    <div>
      <p>API is {isHealthy ? 'up' : 'down'}</p>
      {responseTime !== null && <p>Response time: {responseTime.toFixed(1)} ms</p>}
      {error && <p>{error}</p>}
      {lastChecked && <p>Last checked: {lastChecked.toLocaleTimeString()}</p>}
      <button onClick={healthCheck} disabled={isChecking}>
        Check now
      </button>
    </div>
  );
};

API

useHealthCheck(url, options?)

Options

| Option | Type | Default | Description | | ----------------- | --------------------------------- | ---------- | -------------------------------------------------------------------- | | interval | number | 30000 | Time between checks, in ms. 0 disables polling (still checks once). | | timeout | number | 5000 | Abort a check that takes longer than this, in ms. | | enabled | boolean | true | Set false to pause checks entirely. | | method | 'GET' \| 'HEAD' | 'HEAD' | HTTP method used for the check. | | onStatusChange | (isHealthy: boolean) => void | — | Called whenever health status transitions. |

Return value

| Field | Type | Description | | -------------- | ------------------------- | ------------------------------------------------ | | isHealthy | boolean \| null | null until the first check resolves. | | isChecking | boolean | true while a check is in flight. | | lastChecked | Date \| null | Timestamp of the most recent check. | | responseTime | number \| null | Latest check time to response headers, in milliseconds. | | error | string \| null | Error message from the most recent failed check. | | healthCheck | () => Promise<void> | Run a check immediately, outside the interval. |

Behavior notes

  • responseTime measures client-observed elapsed time until response headers arrive, including network latency, for both successful and non-2xx responses. It does not measure body download or server processing alone. The previous value remains while checking; it is null initially and after offline, network-error, or timeout checks.
  • A check counts as unhealthy on any non-2xx response, a network error, or a timeout.
  • If navigator.onLine is false, the hook reports unhealthy without making a network request.
  • In non-browser environments (SSR), the hook is a no-op and isHealthy stays null.

License

MIT