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

daemon-command-webpack-plugin

v1.5.0

Published

Run or restart npm commands after webpack build has finished

Downloads

2

Readme

daemon-command-webpack-plugin

license travis AppVeyor npm npm

This is simple webpack plugin that monitors webpack events and start or restart npm/yarn command. The main purpose of this plugin is to restart node process when webpack has finised rebuilding the source tree. It is also possible to wait for the marker to make sure the process is finished doing the job (like starting the web server)

Installing as a package

Use NPM: npm i daemon-command-webpack-plugin -D or npm install daemon-command-webpack-plugin --save-dev

Use YARN: yarn add daemon-command-webpack-plugin --dev

Usage

// package.json

{
  "name": "me-app",
  "version": "1.0.0",
  "scripts": {
      "start:dev:env": "node server/build/index.js",
      "start:dev": "NODE_ENV=development PORT=3000 node server/build/index.js",
    },
}
// webpack.config.js

import DaemonCommandPlugin from 'daemon-command-webpack-plugin';

module.exports = {
  // ... rest of config
  plugins: [
    // Command #1
    new DaemonCommandPlugin('start:dev:env', {
      spawn : {
        env : {
          NODE_ENV : 'development',
          PORT : 3000
        }
      }
    }),
    // Command #2
    new DaemonCommandPlugin('start:dev');,
    // Command #3 use yarn
    new DaemonCommandPlugin('start:dev', {
      manager : 'yarn'
    });
  ]
}

Usage with marker

// webpack.config.js

import DaemonCommandPlugin from 'daemon-command-webpack-plugin';

module.exports = {
  // ... rest of config
  plugins: [
    // Command #1
    new DaemonCommandPlugin('start:dev', {
      marker : true
    });
  ]
}
// your-app.js

import express from 'express';
import marker from 'daemon-command-webpack-plugin/marker';

let app = express();

app.listen(8080, () => {
    console.log('Listen port: 8080');
    marker();
    // or
    marker('Listen port: 8080'); // Custom message
})

Arguments

  • command <String> The package.json scripts command to run
  • options <Object>
    • event <String> Webpack life cycle event. Default: after-emit
    • marker <Boolean> Resolve promise when a marker is found to stdout. Default: false
    • spawn <Object> Spawn options
      • cwd <String> Current working directory of the child process
      • env <Object> Environment key-value pairs
      • argv0 <String> Explicitly set the value of argv[0] sent to the child process. This will be set to command if not specified.
      • stdio <Array> | <String> Child's stdio configuration. (See options.stdio)
      • detached <Boolean> Prepare child to run independently of its parent process. Specific behavior depends on the platform, see options.detached)
      • uid <Number> Sets the user identity of the process
      • gid <Number> Sets the group identity of the process
      • shell <Boolean> | <String> If true, runs command inside of a shell. Uses /bin/sh on UNIX, and cmd.exe on Windows. A different shell can be specified as a string. The shell should understand the -c switch on UNIX, or /d /s /c on Windows. Defaults to false (no shell).

Use cwd to specify the working directory from which the process is spawned. If not given, the default is to inherit the current working directory. Use env to specify environment variables that will be visible to the new process, the default is process.env.

Marker arguments

License

MIT