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

rollup-plugin-hot-css

v0.7.2

Published

CSS loader for Rollup with HMR support for Nollup.

Downloads

196

Readme

rollup-plugin-hot-css

A generic CSS loader for Rollup. Supports Hot Module Replacement when used with Nollup. If the CSS imports any assets such as images or fonts, those URLs are resolved with assets emitted.

How to use

npm install rollup-plugin-hot-css
let hotcss = require('rollup-plugin-hot-css');

module.exports = {
    ...
    plugins: [
        hotcss({
            file: 'styles.css',
            extensions: ['.css', '.scss'],
            loaders: ['scss'],
            hot: true
        })
    ]
}

Options

  • String file - Output file name. Default is styles.css. The final name of this file will be based on assetsFileName Rollup output option.

  • Array extensions - Extensions to run the plugin for. Default is .css, .scss, .less

  • Function loaders - Array of preprocessors to run. Can accept either a string or a function. The only supported strings are scss and less (note: they must be installed). Passing a custom loader can be done using a function. The function will receive input and id. input will contain code and map with the code and sourcemap so far.

  • Boolean hot - Enable hot module replacement using <link> tag. This should be disabled if building for production. Default is false.

  • Boolean url - Enable resolving URLs found in CSS file and export those assets. This will resolve after all other loaders. Sourcemaps must be emitted by the previous loader for this to work. Default is true.

  • String publicPath - Used by HMR. If the app is not being hosted on the root of the domain but instead in a subdirectory, use this option to provide the path prefix. Default is /.

Loaders

There are two built in loaders: scss and less. Custom loaders can be specified, as described below:

function MyCustomLoader (input, id) {
    // input.code
    // input.map
    // input.watchFiles

    return {
        code: /* transformed code as a string */,
        map: /* source map */,
        watchFiles: /* optional extra files to watch for changes */
    }
}

hotcss({
    loaders: ['scss', MyCustomLoader]
})

Loaders can also be asynchronous by returning a Promise:

function MyCustomLoader (input, id) {
    return new Promise(resolve => ({
        code: /* transformed code as a string */,
        map: /* source map */,
        watchFiles: /* optional extra files to watch for changes */
    }));
}

An example using postcss:

let autoprefixer = require('autoprefixer')
let postcss = require('postcss')

function PostCSSLoader (input, id) {
    return postcss([autoprefixer]).process(input.code).then(res => {
        return {
            code: res.css
        };
    });
}

hotcss({
    loaders: ['scss', PostCSSLoader]
})

Hot Module Replacement

The HMR API expects there to be a link tag inside the index.html file.

<link rel="stylesheet" type="text/css" href="/styles.css">

When file changes are made, the link tag is replaced by appending a timestamp to the end of the href. This forces the browser to download the file again.

Note that the href is based on the assetsFileName option. If using Nollup for example, if your assetsFileName option is set to [name].[hash][extname] then href should be set to /styles.[hash].css.