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

post-command-hook

v2.0.2

Published

Run a command and then all registered hook(s)

Downloads

8

Readme

post-command-hook NPM version

Run a command and then all registered hook(s).

Installation

$ npm install --save post-command-hook

or

$ yarn add post-command-hook

Usage

Let's suppose we want to add esdoc to our project, create config file and generate a documentation. To achieve that we could create a file esdoc-setup.js and use the following snippet:

const PostCommandHook = require('post-command-hook');

const postCommandHook = new PostCommandHook({ command: 'npm', args: ['i', '--save-dev', 'esdoc', 'esdoc-standard-plugin'] });
postCommandHook.use(() => {
  require('fs').writeFile("./.esdoc.json", `{
    "source": "./lib",
    "destination": "./docs",
    "plugins": [{"name": "esdoc-standard-plugin"}]
  }`, (err) => {
    if (err) {
      console.log(err);
    }
  });
}).use({ command: './node_modules/.bin/esdoc' });

(async () => {
  await postCommandHook.run();
})();

and run it:

$ node esdoc-setup.js

API

new PostCommandHook(baseCommand, execaOptions)

Constructs an instance of PostCommandHook class providing baseCommand and execaOptions. The baseCommand is an object with the following keys:

baseCommand

Type: object

Base command to be issued. It must have required command key, args is optional one.

command

Type: string Required: true

A command that should be issued.

args

Type: array

A command arguments to construct the whole command.

premessage

Type: string

A message to be displayed before execution of the specified command.

postmessage

Type: string

A message to be displayed after execution of the specified command.

execaOptions

Options to be used while executing a command. Default value is { stdio: "inherit" }. See execa documentation for details.

.use(plugin)

Registers specified plugin that will be issued after execution of the base command. Could be chained.

plugin

Type: object, function or an instance of class responding to .run.

.setRunOnce(value)

Instructs to keep already performed commands in the registry and not to run them again. It allows you to add a plugins which are going to be ran without executing previously issued commands.

value

Type: boolean

Whether to issue a commands which are previously have been executed.

.run(options)

Executes the base command and then executes all registered plugins.

options

Type: object

skipErrors

Type: boolean

Instructs to not throw an error if any happens and silently skip it. Note that this option will not apply for base command execution hence if base command fails an error will be thrown.

License

MIT © Rushan Alyautdinov