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

simple-css-hmr

v1.1.0

Published

Simple css hot module reloading without webpack

Readme

Simple css hmr

Simple css hmr provides a simple way of automatically refreshing css in the browser, whenever the source file changes. This can be extremely useful with homegrown frameworks that doesn't support webpack hmr. Pages that uses these frameworks can often take a while to instantiate. Or it might be useful simply because the part of the page that is currently being designed takes a while to open due to some complex state that needs to be created, say a very dynamic editor.

Configure the client

To use simple css hmr a couple of small changes are needed in the client.

First, you need to either add dist/main.js to the page, or include it using a bundler like webpack. If you are using a module system like amd, commonjs or es6 modules, then the library also supports imports these ways. Simple import the dist file.

Once that is done, a single method call to setupCssHmr is all that is needed:

setupCssHmr({
    hmrLink: 'ws://localhost:8796',
    cssLinkTagSelector: '#replaceable-css-link'
});

hmrLink is the websocket link to the server, see 'Configure the server'.
cssLinkTagSelector is a selector to get link that currently loads the css file. see example.

Configure the server

The server can be configured in two ways, either using the command line interface or programmatically.

Via cli

To setup the server using the cli, do simple-css-hmr <filename> where <filename> is the name of the build css file that should be watched. e.g. simple-css-hmr example/text.css.
If your css file name changes after each build, (e.g. webpack file hashes) then you can also watch the entire folder by only passing in the folder name instead of the entire file path. e.g. simple-css-hmr example.

Programmatically

To activate the server programmatically, maybe as a part of your webpack setup, do the following:

var startServer = require('simple-css-hmr/server/server').startServer;

startServer(options);

the options object has the following properties:

interface IOptions {
    /**
     * The port to run the simple-css-hmr server on
     */
    port: number;
    /**
     * Any files or folders to watch
     */
    files: string[];
    /**
     * If the server should actively push the new css content to the client
     * or if the client should fetch it themselves. The default client will dynamically
     * handle this without any additional configuration required.
     */
    push: boolean;
    /**
     * Time to wait before sending refresh to browser (in ms)
     */
    delay: number;
}