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

sweet-path

v3.0.0

Published

Tiny, type-safe utility for filling :param placeholders in URL paths. Around 1kb before gzip.

Readme

Sweet Path npm package

Sweet Path is a tiny, type-safe utility for filling :param placeholders in URL paths.

Features

  • Tiny: around 1kb before gzip, zero runtime dependencies
  • TS Safe: parameters are inferred from a path

Install

npm install sweet-path

Usage

import { SweetPath } from "sweet-path";

const route = new SweetPath("https://api.com/users/:id");

route.insert({ id: 10 });
//             ^^ "id" inferred from the path - autocompleted and required
// "https://api.com/users/10"

route.original;
// "https://api.com/users/:id"

Multiple params:

const route = new SweetPath("https://api.com/books/:bookId/authors/:authorId");

route.insert({ bookId: 10, authorId: 20 });
//             ^^^^^^      ^^^^^^^^ inferred from the path - autocompleted and required
// "https://api.com/books/10/authors/20"

No params - insert() takes no arguments:

const route = new SweetPath("https://api.com/health");

route.insert();
//     ^^^^^^ path has no params, so insert() takes no arguments
// "https://api.com/health"

Type safety

You do not need to specify the path params, as they inferred from the string you are providing, and for usage you have to specify the exact parameters that were inferred:

const route = new SweetPath("https://api.com/books/:bookId/authors/:authorId");

route.insert({ bookId: 10, authorId: 20 }); // ✅ ok

route.insert();               // ❌ params required
route.insert({});             // ❌ missing bookId, authorId
route.insert({ bookId: 10 }); // ❌ missing authorId

Param values may be string, number, or boolean, and are URL-encoded:

new SweetPath("https://api.com/search/:term").insert({ term: "a/b c" });
// "https://api.com/search/a%2Fb%20c"

API

new SweetPath(path)

path - a URL or path template. Params are segments written as /:name.

insert(params?)

Replace path parameters, and returns a string. When the path has no params, call insert() with no arguments. Unknown : tokens that are not path segments (e.g. a :8080 port) are left untouched.

original

The original template string, unchanged.