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

hyperscript-css-modules-injector

v0.1.1

Published

Inject CSS Modules' stylenames transparently into hyperscript via this webpack loader

Readme

hyperscript-css-modules-injector

npm

Automatically transform this:

import h from 'preact-hyperscript-h'
import style from './style.styl'

h('div.class', {}, ...)

into this:

import h from 'preact-hyperscript-h'
import style from './style.styl'

h(`div.class.${style['class']}`, {}, ...)

with this webpack loader!

It adds CSS Modules's classnames exported from style file automatically to the hyperscript's tag (1st) argument.

Install

npm i hyperscript-css-modules-injector

Usage

In your webpack.config.js:

{
  loaders: [{
    test: /\.js$/,
    include: sourceDir,
    loader: [
      'babel-loader',
      'hyperscript-css-modules-injector',
    ],
  }]
}

In your component

├───index.js
└───style.styl

Make sure your index.js imports style.styl (possible extensions: /.*(?css|sass|less|styl)/) as style and uses h (from preact-hyperscript), exactly like this:

import {createElement as h} from 'preact-hyperscript';
import style from './style.styl';

export default h('div.class', {}, [...])

Detailed usage

If you're using preact-hyperscript and CSS with webpack like this:

some-component.js:

import {createElement as h} from 'preact-hyperscript';
import style from './style.styl';

export default h('div.class', {}, [...])

style.styl:

.class
  background: yellow

And you've configured you css-loader in webpack to use CSS Modules (modules: true) then you'll know that you have to somehow assign the value of style.class in your js file as a class name in your hyperscript component. Either by simply doing h('div', {class: style.class}, [...]) or by using things like hyperstyles (or hyperstyles-loader) (or in React/JSX you may have used react-css-modules).

This module tries to transparently apply the classname in your component with a simple regex-replace (at least for now).

So the above would be transformed to:

some-component.js:

import {createElement as h} from 'preact-hyperscript';
import style from './style.styl';

export default h(`div.class.${style.class}`, {}, [...])

It automatically transforms h('div.class') into h(`div.class.${style['class']}`)

Right now it's logic is very simple. It replaces /h('(.*)\.(.*)')/g to h(`$1.${style.$2}`) in regex.

Future plans

  • More versatile syntax parsing. Currently it only replaces h('<tagname>.<class>'). There may be loads of different use cases.
  • Make it work with hyperscript. Currently it only works if h can parse classnames from 1st argument (preact-hyperscript).

Other solutions: