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

isom

v2.1.3

Published

Command line task runner

Downloads

26,363

Readme

Isom

Take your task runner further

If you have a tasks.json file running isom or npx isom will run the task you pass in or the start task.

Lifecyle

For every task you can define you can also have a pre post as well as a cleanup associated with it.

  • pre runs before the main command.
  • command runs if the pre command is successful
  • post runs if the command was successful
  • clean runs regardless of the success or failure of the other tasks

Example

The tasks.json file

{
  "prebuild": ["npx eslint ./src", "npx jest", "rm -rf dist"],
  "build": "npx webpack --config ./src/webpack/prod.config.js --mode production",
  "postbuild": ["npm publish", "npx publisher", "node ./src/tasks/announce.js"],
  "cleanupbuild": "rm -rf dist"
}

Then from the command line you can either run npx isom build or if installed globally isom build

You can use it within your scripts so in your package.json

{
  "build": "isom build"
}

Parallel Tasks

In addition to single items, a task can be an array of items. If the array is a pretask they execute in a series, however if the array is the main task to run, the tasks run in parallel.

Example

{
  "predev": [
    "docker-compose -f ./docker/docker-compose.yml up --detach",
    "node ./src/scripts/delay.js",
    "npx knex migrate:latest",
    "npx knex seed:run"
  ],
  "dev": [
    "nodemon ./src/server/index.js",
    "webpack-dev-server --config ./src/webpack/dev.config.js --mode development"
  ]
}

Then from command line

isom dev

Then the predev tasks run in order then then dev task executes both tasks at the same time.