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

@sidekick-coder/lab

v2.1.6

Published

A developer-friendly CLI for managing and running typed commands globally, eliminating the hassle of node_modules in every project

Readme

@sidekick-coder/lab

A developer-friendly CLI for managing and running commands globally

  • No need for node_modules but still keeps type safety
  • Modular commands with lab.mjs files
  • Default modules for common tasks

Installation

You can install globally using npm:

npm install -g @sidekick-coder/lab

Or use it directly with npx (no install required):

npx @sidekick-coder/lab [command]

Usage

After installing globally, run the CLI with:

lab [command]

Or, if using npx:

npx @sidekick-coder/lab [command]

Setting up an Alias

To make it easier to use, you can set up a shell alias. Add the following to your shell profile (e.g., .bashrc, .zshrc, or PowerShell $PROFILE):

Bash/Zsh

# npx
alias lab="npx @sidekick-coder/lab"

# global install 
alias lab="node $(npm root -g)/@sidekick-coder/lab/index.js"

PowerShell

# npx
function lab {
    npx '@sidekick-coder/lab' @args
}

# gloabl install 
function lab {
    $root = npm root -g
    $path = Join-Path -Path $root -ChildPath "@sidekick-coder/lab/index.js"

    node $path @args
}

Now you can use lab as a shortcut for the CLI.

Labs

Labs are modular JavaScript files that extend the CLI with custom subcommands. You can initialize a new lab in your project with:

lab init [name]

This generates a tsconfig.json, a lab.mjs entry point, and a sample command.

A typical lab.mjs registers your lab and its subcommands:

import { createCommander } from '@lab/core/commander/index.js'
import { defineLab } from '@lab/utils/index.js'
import { resolve } from 'path'

export default defineLab({
    name: 'my-lab',
    setup(lab) {
        const commander = createCommander({
            bin: `${lab.commander.bin} my-lab`,
        })
        commander.addFolder(resolve(import.meta.dirname, './commands'))
        lab.commander.addSubCommander('my-lab', commander)
    },
})

You can register labs globally by adding their paths to your home config file (e.g., ~/.lab/config.yml):

labs:
  - /absolute/path/to/my-lab.mjs
  - /absolute/path/to/another-lab.mjs

For more details, see the full Lab Registration Guide.

License

MIT