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-fail-plugin

v2.0.0

Published

Webpack plugin that makes the process return an error code on failure

Downloads

5,292

Readme

DEPRECATED: This is default behaviour in Webpack 2.x, you probably don't need this plugin anymore.

If you're using Webpack 2+ then you shouldn't need this plugin anymore. Under normal circumstances Webpack should already exit with a proper exit code. As such, this plugin does not officially support Webpack 2+.

If you don't get the correct exit code with Webpack 2+ then this is most likely a bug in a plugin you're using, or you're running into a Webpack bug. In either case I strongly recommend to isolate the problem and file issues at the appropriate repositories. In the mean time you could try to use this plugin as a temporary workaround.

Description

Webpack plugin that will make the process return status code 1 when it finishes with errors in single-run mode.

Install

npm install webpack-fail-plugin --save-dev

Usage

var failPlugin = require('webpack-fail-plugin');

module.exports = {
	//config
	plugins: [
		failPlugin
	]
}

Credits to @happypoulp.