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

las-webpack

v1.0.1

Published

Webpack plugin that integrates LAS CSS with LAS Engine to emit utilities on the fly.

Readme

las-webpack

Webpack plugin for LAS CSS + LAS Engine. Scans your project, JIT-generates only the utility classes you use, serves a virtual module in dev, and outputs inline or external CSS in production.

Install

npm install -D lascss las-webpack
pnpm add -D lascss las-webpack
yarn add -D lascss las-webpack

Usage

webpack.config.js:

// CommonJS
const lascss = require("las-webpack").default;
// ESM
import lascss from "las-webpack";

module.exports = {
  plugins: [
    new lascss({
      scanDirs: ["src"],           // default: ["src"]
      extensions: [".tsx", ".jsx"],// merged with defaults
      ignoreDirs: ["dist"],        // merged with defaults
      // output: "assets/las.css", // write a file in prod and link via HtmlWebpackPlugin
    }),
  ],
};

App entry:

import "las.css"; // plugin swaps the virtual module with generated CSS

How It Works

  • LAS Engine scans scanDirs and CSS/SCSS files, then builds CSS for used classes.
  • Dev: CSS is written to the las.css virtual module with HMR updates.
  • Prod:
    • Without output: CSS stays inline (virtual module can be empty if you don’t use style-loader).
    • With output: CSS is emitted as a file; if HtmlWebpackPlugin is present, a link rel="stylesheet" is injected automatically.

Options (LasEngineOptions)

  • scanDirs: Directories to scan. Default: ["src"].
  • extensions: Content extensions (merged with html/js/ts/vue/svelte defaults).
  • cssExtensions: CSS/SCSS extensions (merged with defaults).
  • ignoreDirs: Directories to ignore (merged with defaults).
  • output: CSS file path for production (e.g., css/las.css).