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

@plumelo/thunder

v1.6.4

Published

A tiny wrapper around lightningcss

Readme

@plumelo/thunder

A tiny wrapper around lightningcss that adds a custom resolver and normalizes CSS module exports.

Install

npm install @plumelo/thunder

Usage

import thunder from "@plumelo/thunder";

const result = await thunder({
  filename: "src/styles.css",
  input: `
    .btn { color: red; }
    .btn--lg { font-size: 18px; }
  `,
});

// result.code       — compiled CSS (Buffer)
// result.map        — source map
// result.classes    — camelCased class name mapping
//   e.g. { btn: "btn", btnLg: "btn--lg" }

Resolving imports

Thunder includes a custom resolver that handles @import resolution using enhanced-resolve:

import thunder, { resolver } from "@plumelo/thunder";

const result = await thunder({
  filename: "src/app.css",
  input: `@import "theme.css";`,
  resolver: resolver({
    extensions: [".css", ".scss"],
  }),
});

API

thunder(options): Promise<ThunderResult>

Wraps lightningcss.bundleAsync with:

  • Automatic targets — defaults to browserslist targets if not specified
  • Custom resolver — uses the built-in resolver by default
  • Normalized exportsresult.classes is a camelCased map of CSS module class names

resolver(options?)

Returns a resolver object for lightningcss's resolver option. Resolves @import specifiers by:

  1. Treating the specifier as a relative path
  2. Appending .css if the specifier has no extension
  3. Falling back to enhanced-resolve (node_modules resolution)

Exports

| Path | Description | |---|---| | @plumelo/thunder | Main API (thunder default export) | | @plumelo/thunder/resolve | Resolver utility (resolver export) |

License

MIT