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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@denwa/do

v1.1.0

Published

Javascript based task runner. build and run tasks with javascript in the same spirit as [Jake](https://www.npmjs.com/package/jake), [Grunt](https://www.npmjs.com/package/grunt).

Readme

@denwa/do

Javascript based task runner. build and run tasks with javascript in the same spirit as Jake, Grunt.

Use when package.json scripts becomes too scary.

GitHub Workflow Status npm (scoped)

Installation

npm install @denwa/do

Usage

create a do.js file in project repo root.

// import functions
let { sh, task, execute } = require('@denwa/do');

// register hello task
task('hello', () => {
	sh('echo hello friend!');
});

// parse arguments and execute tasks
execute();

execute hello task with following command

$ node do hello
hello friend!

API

sh

execute a shell command, works the same as child_process.execSync except that it catches an exit code of 130 and exits the current process.

function sh(command: string | string[], options: ExecSyncOptions): void

task

register a task callback to be executed, the callback can be sync or async and takes a minimist ParsedArgs object

function task(name: string, callback: (args?: ParsedArgs) => void | Promise<void>): void

execute

executes the tasks register by parsing the command line arguments and invoking the requested task names

async function execute(args?: string[]): Promise<number>

Command Line

node <script> <tasks> <options?>

where

| Parameter | Description | | --------- | -------------------------------------------------------------- | | script | name of script file to execute, see do.js example in Usage | | tasks | one of more space separate task names to execute | | options | task specific options |