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

webpack-clean-css-after-compile-plugin

v1.0.1

Published

Webpack Plugin for clean-css minification after compilation.

Downloads

25

Readme

Webpack Clean CSS After Compile Plugin

For some reason webpack.optimization with CssMinimizerPlugin.cleanCssMinify does not work as expected. This plugin aims to solve the same thing but after compilation is done. The css assets are modified in place without altering the references already set by webpack.

Installation

npm i -D webpack-clean-css-after-compile-plugin

Configuration

The plugin takes a single argument as object having:

{
    isProduction: boolean, // if true will run minification, else not
    outputDir: string, // must match the webpack output path
    cleanCssOptions: object, // optional, default is empty object
}

For detailed cleanCssOptions see clean-css documentation.

Usage

The following example shows a minimal scenario

const path = require('path');
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
const CleanCssAfterCompilePlugin = require('webpack-clean-css-after-compile-plugin');

// see clean-css docs for options, the following is default and is not required
const cleanCssOptions = {};

const isProduction = process.env.NODE_ENV === 'production';
const sourceDir = path.resolve(__dirname, 'src');
const outputDir = path.resolve(__dirname, 'web');

module.exports = {
    mode: isProduction ? 'production' : 'development',
    entry: { index: path.resolve(sourceDir, 'index.js') },
    output: {
        path: outputDir,
        // other options
        clean: true,
    },
    module: {
        rules: [
            {
                test: /\.css$/i,
                // options.publicPath is required for asset imports in CSS, such as url()
                use: [{ loader: MiniCssExtractPlugin.loader, options: { publicPath: '' } }, 'css-loader' ],
            },
        ],
    },
    plugins: [
        new MiniCssExtractPlugin({/* options */}),
        new CleanCssAfterCompilePlugin({ isProduction, outputDir, cleanCssOptions }),
    ],
    devtool: isProduction ? false : 'source-map',
};