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

@sketchyicons/data

v0.5.0

Published

Hand drawn icon geometry, derived from Lucide. No framework, no dependency.

Readme

@sketchyicons/data

The geometry behind sketchyicons, with no framework and no dependency. Every framework package is generated from this one.

npm install @sketchyicons/data

Use

Reach for this when you are rendering the icons yourself: a framework nobody has written a target for yet, a canvas, a PDF, a plotter.

import { House, iconNames } from '@sketchyicons/data';
import type { IconNode, IconName } from '@sketchyicons/data';

// [['path', { d: 'M14.72 21.05Q16.02 17 ...' }], ...]
const svg = `<svg viewBox="0 0 24 24" fill="none" stroke="currentColor"
  stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
  ${House.map(([, attributes]) => `<path d="${attributes.d}" />`).join('')}
</svg>`;

Icons are named constants rather than one module each, so a bundler drops the ones nobody imported. One icon costs 250 bytes minified and brotlied.

What it exports

| Export | Type | What it holds | | --------------------------------- | -------------------------- | ------------------------------------------------------ | | House, Star, and one per icon | IconNode | the drawn geometry | | iconNames | readonly IconName[] | every name in kebab case, in name order | | componentNames | readonly ComponentName[] | the same names as the framework packages export them | | renamed | readonly [old, now][] | the 247 names Lucide has renamed, and what they became | | IconNode | type | [tag, attributes][] | | IconNodeAttributes | type | Record<string, string \| number> |

IconNode is the shape Lucide uses, so their createLucideIcon accepts one of ours unchanged.

Every path draws with fill="none", stroke-linecap="round" and stroke-linejoin="round" on a 0 0 24 24 viewBox. A path that carries its own fill is meant to be filled, and there are a handful: small dots that read as a ring without it.

Where it comes from

The geometry is derived from Lucide once per upstream release, not on every build. Straight runs bow, coordinates drift, and the drift is seeded from the icon name, so the same name always draws the same glyph.

Licence

MIT for the code, see LICENSE. The geometry is derived from Lucide and keeps Lucide's ISC terms, see NOTICE. Not affiliated with Lucide.