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

alarmist-webpack

v1.0.11

Published

Wrap webpack watch in alarmist jobs

Downloads

4

Readme

alarmist-webpack

Build Status Build status Coverage Status

Wrap webpack watch in alarmist jobs

Usage

As this is a tool linking webpack with alarmist, it is expected that your project already has both alarmist and webpack installed

npm install webpack alarmist alarmist-webpack

You can then add something like the following to your package.json scripts

{
  ...
  "scripts": {
    ...
    "alarmist:build": "alarmist-webpack -n job-name -c ./path/to/webpack/config",
    ...
  },
  ...
}

Then add that script to the watch jobs started by alarmist-monitor.

Usage: alarmist-webpack [options]

Start webpack in watch mode. The working directory
should match the working directory of the monitor and usually this will
be the default. If the job is started via a watcher started
by the monitor then the 'ALARMIST_WORKING_DIRECTORY' environment
variable will have already been set.

Environment Variables:

FORCE_COLOR
ALARMIST_WORKING_DIRECTORY
ALARMIST_WEBPACK_NAME
ALARMIST_WEBPACK_CONFIG

Options:
    --name, -n            The name to use for the job (default: "webpack")
    --working-dir, -w     The directory in which to write logs, etc (default: ".alarmist")
    --config, -f          webpack config file path (default: "webpack.config.js")
    --colors, -c          turn on colors for webpack stats report (default: true)
    --help, -h            Show help
    --version, -v         Show version number

Contributing

Run lint, tests, build, etc before pushing/submitting PRs

  • npm test - lint and test
  • npm run build - run tests then build
  • npm run watch - watch for changes and run build
  • npm run ci - run build and submit coverage to coveralls
  • npm start - watch for changes and build, lint, test, etc in parallel with alarmist