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

filter-entry-output-plugin

v1.0.0

Published

Webpack plugin to filter output files based on the entry points.

Downloads

3

Readme

filter-entry-output-plugin

Webpack plugin to filter output files based on the entry points.

Installation

yarn add filter-entry-output-plugin -D

Usage

Use the plugin to remove unwanted output files, such as JS stubs that are getting created when abusing webpack as a pure SASS compiler. For example, in the following scenario normally not only a theme.css but also a theme.js file would get emitted for the theme entry point; the plugin can be used to remove those unnecessary webpack bootstrap files from SCSS-only entry points:

// webpack.config.js
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const FilterEntryOutputPlugin = require('filter-entry-output-plugin')
const path = require('path')

module.exports = {
  entry: {
    main: './src/index.js',
    theme: './src/theme.scss'
  },
  output: {
    filename: '[name].js',
    path: path.join(__dirname, 'dist')
  },
  module: {
    rules: [{
      test: /\.scss$/,
      use: [
        MiniCssExtractPlugin.loader,
        'css-loader',
        'sass-loader'
      ]
    }]
  },
  plugins: [
    new MiniCssExtractPlugin({
      filename: '[name].css'
    }),
    new FilterEntryOutputPlugin({
      test: /\.scss$/,
      remove: /\.js$/,
    })
  ],
}

Options

  • test -- The entry files for which the output should get filtered.Type: RegExpDefault: /\.(c|sc|sa)ss$/
  • remove -- The output files that should get removed, as specified in the filename options of the output and plugin configurations etc.Type: RegExpDefault: /\.js$/
  • exclude -- Exclude entry files (overrides test).Type: RegExp|booleanDefault: false
  • keep -- Output files to keep (overrides remove).Type: RegExp|booleanDefault: false
  • multi -- Whether multi-main entry points should get filtered too.Type: booleanDefault: false

Alternatives

You might also have a look at the FilterChunkWebpackPlugin for another approach based purely on output file patterns.

License

MIT @ m3g4p0p