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

@barretter/remove-unused-files-webpack-plugin

v3.5.0

Published

Glob all files that are not compiled by webpack under webpack's context

Downloads

220

Readme

remove-unused-files-webpack-plugin

fork from unused-files-webpack-plugin。The main extension is to remove unused files.

Version Travis CI Quality Coverage Dependencies Gitter

Install with npm:

npm i --save-dev @barretter/remove-unused-files-webpack-plugin

Install with yarn:

yarn add --dev @barretter/remove-unused-files-webpack-plugin

Usage

webpack.config.babel.js

import RemoveUnusedFilesWebpackPlugin from "@barretter/remove-unused-files-webpack-plugin";

export default {
  plugins: [
    new RemoveUnusedFilesWebpackPlugin(options),
  ],
};

webpack.config.js

const RemoveUnusedFilesWebpackPlugin = require("@barretter/remove-unused-files-webpack-plugin").default;

module.exports = {
  plugins: [
    new RemoveUnusedFilesWebpackPlugin(options),
  ],
};

Options

new RemoveUnusedFilesWebpackPlugin(options)

options.patterns

The (array of) pattern(s) to glob all files within the context.

options.failOnUnused

Emit error instead of warning in webpack compilation result.

  • Default: false
  • Explicitly set it to true to enable this feature

options.globOptions

The options object pass to second parameter of glob-all.

globOptions.ignore

Ignore pattern for glob. Can be a String or an Array of String.

globOptions.cwd

Current working directory for glob. If you don't set explicitly, it defaults to the context specified by your webpack compiler at runtime.

options.removeToBackup

Whether to move unused files to the backup folder. Use this feature with caution.

  • Default: false
  • Explicitly set it to true to enable this feature

backupOptions.backUpDirPath

Backup folder Path.

  • Default: ./.backup
  • Only removeToBackup configuration to be true, This configuration item is valid.

backupOptions.backUpDirname

Backup folder name.

  • Default: The time when you run this plugin
  • Only removeToBackup configuration to be true, This configuration item is valid.

backupOptions.overwrite

Whether to overwrite older files when the backup folder exit the same file

  • Default: false
  • Explicitly set it to true to enable this feature
  • Only removeToBackup configuration to be true, This configuration item is valid.

Contributing

devDependency Status

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request