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 🙏

© 2024 – Pkg Stats / Ryan Hefner

no-undefined-style-loader

v1.0.0

Published

Webpack loader that warns when an undefined key is referenced on a required CSS file

Downloads

2

Readme

CircleCI styled with prettier

no-undefined-style-loader

Webpack loader that warns when an undefined class name is referenced on a CSS file you imported into JavaScript. Works when chained after css-loader with the modules option enabled.

I’ve found it’s painfully easy to mistype class names (or just forget to write the CSS rule I intended to reference), and it’s not always immediately obvious what went wrong. This tool intends to catch those mistakes faster than you would by hand.

This loader is not intended to be used in production.

Usage

// webpack.config.js (Webpack 2 syntax shown)

export default {
  entry: './app',
  module: {
    rules: [{
      test: /\.css$/,
      use: [{
        loader: 'style-loader'
      }, {
        loader: 'no-undefined-style-loader',
        options: {
          fail: true // default: false
        }
      }, {
        loader: 'css-loader',
        options: { modules: true }
      }
    }]
  }
}
/* app.css */

.hide {
  display: none;
}
// app.jsx

import React from 'react';
import ReactDOM from 'react-dom';
import styles from './app.css';

// This works as usual
ReactDOM.render(
  <div className={styles.hide} />,
  document.getElementById('app')
);

// This results in a warning or error
ReactDOM.render(
  <div className={styles.thisClassNameObviouslyDoesNotExist} />,
  document.getElementById('app')
);

The browser console will warn the developer:

Warning: CSS class `.thisClassNameObviouslyDoesNotExist` not found in `/Users/you/path/to/app.css`.

Options

  • fail: boolean = false When false, accessing undefined class names warns with console.error. When true, attempting to access an undefined class name throws an error.

Browser support

This loader relies on Proxies, which have good support in modern browsers. If Proxies are unavailable, the loader will emit a warning in the browser console and then do nothing.