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

@kranehq/yard

v0.0.6

Published

CLI for routing local dev servers to stable *.localhost hostnames

Readme

Yard

Yard gives each local app a stable *.localhost hostname so you can run multiple projects without port juggling.

Packages

  • @kranehq/yard: CLI that starts your command with YARD_* env vars and proxies traffic from <name>.localhost:<publicPort>.
  • @kranehq/yard-vite: Vite plugin that reads Yard env vars and configures the dev server for Yard.

Install

bun add -g @kranehq/yard

Quick Start

  1. Configure your dev server to use YARD_PORT and YARD_HOST.
  2. Start it through Yard:
yard -n myapp -- bun run dev
  1. Open:
http://myapp.localhost:3000

CLI

$ yard --help
Yard routes local dev servers to stable *.localhost hostnames.

Usage:
  yard [options] -- <command> [args...]

Options:
  -n, --name <name>      Project hostname prefix (required unless in config)
  -p, --port <port>      Public proxy port (default: 3000)
  -c, --config <path>    Config module path (default: ./yard.config.ts)
  -h, --help             Show help

Examples:
  yard -n myapp -- bun run dev
  yard -n api -p 4000 -- bun run dev
  yard -c ./yard.config.ts -- bun run dev

Environment Variables Passed To Your Command

  • YARD_HOST: <name>.localhost
  • YARD_PORT: allocated internal port for your dev server to bind to
  • YARD_PUBLIC_PORT: external proxy port

Config File

By default, Yard reads yard.config.ts as an ESM module.

export default {
    name: "myapp",
    port: 3000,
};

Flags override file values.

Vite Plugin

Install:

bun add -d @kranehq/yard-vite

Configure:

import { defineConfig } from "vite";
import { yard } from "@kranehq/yard-vite";

export default defineConfig({
    plugins: [yard()],
});

Run through Yard:

yard -n myapp -- bun run dev