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

path-kv

v0.0.6

Published

[![janwilmake/cloudflare-assets-kv context](https://badge.forgithub.com/janwilmake/cloudflare-assets-kv)](https://uithub.com/janwilmake/cloudflare-assets-kv)

Readme

path-kv

janwilmake/cloudflare-assets-kv context

This library allows to add a single line to your fetch handler to serve dynamic assets from KV with the following rules:

  • Assets must be saved at the full path you would normally save assets in public, including /index and .html|md etc.
  • If extension was provided, will only check the full path
  • Will look for /index.{ext} if your path ends with a /
  • If extension wasn't provided, will parse accept header and look for most logical .{ext} based on the correct priority.
  • If accept header is */* or not provided, will look for all available in this order: txt, md, json, html

It requires env.PATH_KV to be a KV with files with keys being the full file paths. Allows optional configurable prefix.

Made this feature request: https://x.com/janwilmake/status/1917123946798793121

Quick Start

  1. Install: npm i path-kv
  2. Create your KV and add it to wrangler using wrangler kv namespace create PATH_KV
  3. Use the middleware in your worker:
import { withPathKv } from "path-kv";

export default {
  fetch: withPathKv(async (request, env, ctx) => {
    // Your worker code here
    return new Response("Not Found", { status: 404 });
  }),
};

Now, any files you make available in your KV will be served directly by your handler. Be sure to add contentType

await env.PATH_KV.put("/index.html", newContent, {
  metadata: { contentType: "text/html" },
});

Helper: Adding static assets from local files

To some it may be useful to quickly add files from public to your kv. For that you can just run npx uploadkv.