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

@hydrafetch/react

v0.1.1

Published

React components for company logos, powered by a Hydrafetch publishable key.

Readme

@hydrafetch/react

npm CI bundle size

React components for company logos, powered by a Hydrafetch publishable key.

738 bytes gzipped. React is a peer dependency. Logos bill against logo pulls, not credits.

Installation

npm install @hydrafetch/react

Quick start

import { HydrafetchProvider, Logo } from '@hydrafetch/react';

export default function App() {
  return (
    <HydrafetchProvider publishableKey={process.env.NEXT_PUBLIC_HYDRAFETCH_PK!}>
      <Logo domain="stripe.com" size={32} theme="auto" />
    </HydrafetchProvider>
  );
}

Create a publishable key in your dashboard and restrict it to your domains.

Components

<HydrafetchProvider>

Holds the key so it is not repeated at every call site.

<HydrafetchProvider publishableKey="hf_pk_..." baseUrl="https://img.hydrafetch.com">
  {children}
</HydrafetchProvider>

Throws on any key that does not begin with hf_pk_, which prevents a secret key reaching a browser bundle.

<Logo>

<Logo domain="stripe.com" size={32} theme="auto" type="icon" fallback="monogram" className="rounded" />

| Prop | Values | Notes | | --- | --- | --- | | domain | required | https://www.stripe.com/pricing is normalised to stripe.com | | size | pixels, up to 512 | adds a 2x srcSet | | theme | light, dark, auto | auto follows the system preference | | type | icon, wordmark | defaults to the mark | | fallback | monogram, 404, transparent | what an unknown domain returns |

Any other image attribute passes through. alt defaults to "{domain} logo" and can be overridden.

theme="auto" reads prefers-color-scheme in the browser and re-renders when the user changes it, which a server-rendered URL cannot do.

useLogoUrl(domain, options?)

Returns the URL string, for background images or a framework's own image component.

const src = useLogoUrl('stripe.com', { size: 64, theme: 'auto' });

Server components

<Logo> is a client component because it reads prefers-color-scheme. In a React Server Component, either place it behind a 'use client' boundary, or render a plain image with an explicit theme:

<img src={`https://img.hydrafetch.com/logo/${domain}?token=${KEY}&size=32&theme=dark`} />

Billing

Logos are metered against logoPullsPerCycle on your plan and never draw on your credit balance, so rendering logos on every page view does not consume the budget used for scraping.

Related packages

Links

License

MIT