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

edev

v1.0.0

Published

Run a series of scripts based on a configuration file and pipe their outputs to the console.

Downloads

4

Readme

edev

Execute multiple scripts in parallel and show their output in a unified console.

edev will read a configuration file and execute the scripts defined there.

Installation

npm install -g edev

Usage

First of all you must initialize the config file. This will create a file named edev.json, in which you can define your scenarios.

By default edev init will populate the config file with some sample scenarios.

edev init

To list all available scenarios run

edev ls

To run a scenario named demo run

edev run demo

The config file

edev.json should be at the root of your project, in the folder where you run edev.

The configuration file looks like this:

{
  "ping": [
        {
            "name": "Ping example1",
            "command": "ping www.example1.com"
        },
        {
            "name": "Ping example2",
            "command": "ping www.example2.com"
        }
    ],
    "list": [
        {
            "name": "List all files",
            "command": "ls -lah"
        }
    ]
}

The first level contains the scenario name: ping and list. You use the scenario name in edev run [SCENARIO NAME]

Each scenario is an array of commands. These commands will be executed in parallel. A command has a name and a command parameter. Name your commands as you please.

License

MIT http://rem.mit-license.org