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

exists-webpack-plugin

v2.1.2

Published

Emits an error if output.path or custom path exists (or not exists)

Downloads

31

Readme

exists-webpack-plugin logo

NPM Version NPM Downloads GitHub issues Telegram

Exists Webpack Plugin

This plugin returns an error (or warning) if specified paths exist (or not exist). Webpack skips the emitting phase whenever there is an error from this plugin. This helps to force the developer to change dist folder and do not overwrite files. The plugin supports the following modes:

  1. Check any custom files or folders if they are exist
  2. Check if output folder exists (to stop Webpack early)
  3. Check if any emitted assets already exist (to prevent overwriting them)
  4. Check files of entry points only (to prevent running the same config twice, but ignore other assets)
  5. Do the same above checks but if files don't exist
  6. Show just warnings instead of errors and let Webpack finish the build

Installation

npm i --save-dev exists-webpack-plugin

Usage

In your webpack configuration

module.exports = {
  // ...
  plugins: [
    new ExistsWebpackPlugin({
      outputPath: true,
    }),
  ],
  // ...
}

The example above emits an error and stops Webpack if output.path from your configuration already exists.

Options

Default options

{
  paths: undefined,
  mode: undefined,
  onExists: true,
  emitWarning: false,
};

paths (array: undefined)

An array of paths that you want to check for existence. You can use paths relative to your current directory. You should specify either paths or mode.

mode (string: output.path | assets | entries)

output.path

Check for output.path (from Webpack config)

assets

Check generated assets

entries

Check entry points only

onExists (boolean: true)

A boolean value to specify when to emit an error. If you want it when your path do not exist, set this option to false.

emitWarning (boolean: false)

By default this plugin will emit an error if the path exists (or not). You can emit a warning instead by setting this option to true. The build process will not fail in this case and your assets will be overwritten.