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

dev-runner

v0.0.3

Published

A development task runner to start dev servers and other task runners in the order you want.

Downloads

6

Readme

DevRunner

A development task runner to start dev servers and other task runners in the order you want.

Install

npm install --save-dev dev-runner

Configuration

interface EventMatcher {
  regex: RegExp;
  actionData: Object | ((str: string) => Object);
}

interface Config {
  [key: string]: {
    dependsOn?: string[];
    preStart?: string;
    start?: string;
    events?: EventMatcher[];
    process?: ((input: EventEmitter, output: EventEmitter) => void);
    watch?: string[];
    readyAfter?: number;
  }
}
  • dependsOn?: string[]: tasks that must be ready before current task. It detects {type: 'ready'} action as a single of ready. If multiple tasks is specified, will wait until all of them is ready before start current task.
  • preStart?: string: shell command to run before start or process.
  • start?: string: long running shell command, typically a watch process. Cannot be appear at the same time as process. If more {type: 'ready'} action is received, current running process will be killed and new one will be started.
  • events?: EventMatcher[]: match string output of preStart and start with an array of regular expression, if matched, defined action will be emitted. This property only works if start or preStart is defined.
    • regex: RegExp
    • actionData: Object | (str: string) => Object Predefined action object, or a function to generate action object based on matched input string.
    • {type: 'ready'} is a special action to notify following tasks current task is ready. It could be emitted multiple times.
  • process?: (input: EventEmitter, output: EventEmitter) => void: Run some custom code, e.g. live reload server.
    • input: EventEmitter: all event will have a type key.
      • {type: 'ready'}
      • {type: 'watch'; changeType: string; path: string}: changeType can be "add", "change", "unlink".
    • output: EventEmitter
  • watch?: string[]: emit file change event to process. Only works if process is defined.
  • readyAfter?: number: emit {type: 'ready'} action after x milliseconds.