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

lasertag

v0.7.0

Published

zero-runtime structural css for jsx with css modules

Readme

Lasertag 👾

zero-runtime CSS structure for JSX components with CSS Modules.

lasertag is a small convention: each exported component owns one sibling .module.css file, that stylesheet exports one root class, and the rendered root tag names the component in kebab case.

import css from "./AppHeaderBar.module.css"

export const AppHeaderBar = () => (
	<app-header-bar className={css.class}>
		<strong>SignalDesk</strong>
	</app-header-bar>
)
app-header-bar.class {
	display: flex;
	align-items: center;
}

Install

pnpm add -D lasertag

Add the types your project needs:

import "lasertag/css-modules"
import "lasertag/react-jsx"

Use lasertag/preact-jsx or lasertag/solid-jsx instead for Preact or Solid.

Check component-owned CSS Modules for unreachable selectors in parallel:

pnpm lasertag check

Remove unreachable selectors in parallel while reporting progress:

pnpm lasertag fix

Both commands accept one quoted glob or a comma-separated set of globs:

pnpm lasertag fix "src/**/*.module.css,examples/**/*.module.css"

Install the VS Code extension from the same npm package:

pnpm lasertag vsix

Pass an editor command when you want to target another VS Code-compatible binary:

pnpm lasertag vsix --target code-insiders

Build the VSIX without installing it:

pnpm lasertag vsix --build-only

Includes

  • CSS Module typing for a single exported class
  • JSX intrinsic types for hyphenated custom elements
  • an optional ESLint plugin at lasertag/eslint-plugin
  • the Refractor analysis library at lasertag/refractor
  • the lasertag CLI and standalone lasertag-lsp language server
  • a bundled VS Code extension with live diagnostics, completions, and cleanup actions
  • a small global CSS starter at lasertag/templates/globals.css
  • authoring and tooling guides in lasertag/docs

License

Lasertag is free and open-source software under the Mozilla Public License 2.0. MPL 2.0 is permissive about using Lasertag and combining it with other code while preserving improvements to MPL-covered files. It is a file-level copyleft license, not a whole-project copyleft license.

In practical terms, you may:

  • use Lasertag for any purpose, including in commercial and proprietary applications;
  • modify and use it privately without sharing those changes; and
  • combine it with code under other licenses. Separate files that contain no MPL-covered code can remain under terms of your choice.

If you distribute modified MPL-covered files, make the source for those files available under MPL 2.0 and preserve the license notices. Mozilla's official MPL 2.0 FAQ explains the intent and common use cases. This summary is not a substitute for the license itself.