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 🙏

© 2026 – Pkg Stats / Ryan Hefner

task-script-support

v2.6.2

Published

Opinionated library for writing task scripts

Readme

task-script-support

A lightweight library for writing task oriented scripts.

Uses the following:

(Note: using the cli tool to generate a new project will install many additional npm packages including tsyringe, figlet, yargs, chalk, dotenv and more)

For using the library directly, see usage.md. The following section demonstrates using the tssc tool to generate and update a new project from a template.

Getting Started

Install the tssc cli tool:

npm i -g task-script-support-cli

Verify installation / check version:

tssc -v

Introduction

📂 New Project

Create a new project with the new command.

tssc new -n "my-awesome-project"

cd ./my-awesome-project && npm i && npm start -- --help

# My Awesome Project CLI Client
#
# Commands:
#   index.ts verify  check the app is working
#
# Options:
#       --version  Show version number                                   [boolean]
#   -d, --debug    enable extra logging                 [boolean] [default: false]
#       --help     Show help                                             [boolean]

Resource Generation

Use the gen command to generate new task, service, or command class.

For example we can generate a new greet task to say hello.

tssc gen --task -n "greet"

Modify the new task to log a message. You can reference the cli args in the task classes.

edit1

If we add a new cli arg we modify the CLIArgs type to reflect that option.

code ./src/types/state.ts

edit2

🔌 Create Command

When a command is generated it prompts for the tasks the command will execute.

tssc gen --command -n "hello command"

# select the greet task, optionally including others and order them as needed

(Note: ordered tasks are exectued sequentially but you can wrap them in square brackets [] for concurrent execution. Mix and match to create sync points and advanced workflows)

We can register the new command in our ./src/index.ts file by adding the import and command to yargs:

// ...

import { HelloCommand } from "./commands/hello-command";

  // ...

  .command(
    "hello",
    "greet the user",
    (yargs) => {
      yargs.option("n", {
        alias: "name",
        type: "string",
        describe: "the name of the user to greet",
      });
    },
    container.resolve(HelloCommand).handler,
  )

and run it to test things out.

npm start -- hello -n "Max Headroom"
# outputs:
# Hello, Max Headroom! Welcome to the app!