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

@homeflare/kit

v0.3.0

Published

Runtime-neutral HomeFlare primitives: typed env parsing, actionable errors, and an HTTP client.

Downloads

640

Readme

@homeflare/kit

Runtime-neutral primitives: environment parsing, errors, and HTTP. Bun-native to consume — the published bundle runs on Cloudflare Workers, Node and Bun alike.

bun add @homeflare/kit     # or: pnpm add @homeflare/kit

Usage

import { parseEnv } from '@homeflare/kit';

const config = parseEnv(
  {
    API_URL: { type: 'string' },
    PORT: { type: 'number', default: 8787 },
    DEBUG: { type: 'boolean', default: false },
  },
  env, // a Worker's env binding, or process.env
);

config.PORT; // number
config.DEBUG; // boolean — 'false' parses as false, not as a truthy string

parseEnv throws EnvError on the first key that is missing or malformed. The error names the key and never the value.

OpenAPI (Workers / HTTP apps)

import { createOpenApiApp } from '@homeflare/kit/openapi';
import { z } from '@hono/zod-openapi';

const app = createOpenApiApp();

⛔ A subpath, never the main entry — Hono must not land in a Node script that only wanted parseEnv. Peers you provide: hono · @hono/zod-openapi · zod. Import z from @hono/zod-openapi, not from zod, or .openapi() is missing.

The document and the request share one schema. A parallel OpenAPI registry that does not validate is two truths.

Development

bun install
bun run check    # lint + types + build + tests
bun run smoke    # pack, install and use the real tarball under bun AND node
bun run verify   # check + smoke — the full pre-publish gate

Changes are versioned with changesets:

bun run changeset   # describe the change; commit the file with your PR

Contributing

See CONTRIBUTING.md for the workflow and the gates, and AGENTS.md for the toolchain rationale behind them.

Found a vulnerability? Please don't open a public issue — see SECURITY.md.

License

MIT © Timothy Schneider