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

@devslab/dds-icons

v0.13.0

Published

DDS icon set — one SVG source (24 grid, currentColor), shipped as files, a sprite and a path-data map

Readme

@devslab/dds-icons

Directional consumers add dds-icon--directional; the packaged direction-policy.json is the source of truth for icons that mirror in RTL and icons whose physical direction must stay unchanged.

🌐 한국어

The DDS icon set — one SVG source per icon (24 grid, currentColor, round caps), shipped in the three shapes consumers actually need. Spec §3.7, as amended by D-013.

| Artifact | Import | For | | --- | --- | --- | | dist/svg/*.svg | @devslab/dds-icons/svg/phone.svg | build pipelines, <img>, design tools | | dist/icons.svg | @devslab/dds-icons/icons.svg | web sprite — <use href="…/icons.svg#dds-phone"> | | dist/icons.js (+ .d.ts) | @devslab/dds-icons | any runtime that builds its own element (RN, createElementNS renderers, SSR) |

import { icons } from "@devslab/dds-icons";

const i = icons.phone; // { viewBox, strokeWidth, set, body }
<!-- inline, inherits the surrounding color and font-size-independent size -->
<button class="dds-iconbtn" aria-label="Call">
  <svg width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor"
       stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
    <!-- icons.phone.body -->
  </svg>
</button>

Two sets

  • core (svg/*.svg, stroke 1.6) — product UI. Names are function-shaped (chevron-down, external-link, globe — the flag-less fallback for a language-picker trigger); the 22 names inherited from the AskLinq widget keep their exact spelling, because renaming them would break live card icons.
  • site (svg/site/site-*.svg, stroke 1.8) — devslab.kr only, drawn for 32–40px marketing display. The site- prefix is part of the name; the folder is only organization.

Rules (enforced by scripts/check-icons.mjs, so CI fails, not review)

  • viewBox="0 0 24 24", width/height 24
  • fill="none", stroke="currentColor", round cap and join
  • no color literal anywhere in the file, and no stroke/fill/style overrides in the body — color and weight are inherited, always
  • stroke width is the set's (1.6 core / 1.8 site); a third value means an icon was dropped in from somewhere else
  • lowercase kebab-case names, no size or color in the name

Not here on purpose

No React/Vue/RN components are generated. Per spec §2 a framework package exists only once that framework's product does; a map of path data is what every consumer can build from today.

Live gallery: preview/icons.html (run pnpm build first).