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

cloudable-cli

v3.0.2

Published

Intelligent AWS infrastructure recommendations for any codebase - analyze and deploy in minutes

Readme

Cloudable CLI

A command-line interface built with oclif for cloud operations and management.

Prerequisites

  • Node.js 18 or higher
  • npm (comes with Node.js)

Installation

From Source

Clone the repository and install dependencies:

git clone https://github.com/Jai-Dhiman/cloudable.git
cd cloudable
npm install
npm run build

Global Installation (for development)

npm link

After linking, you can run cloudable from anywhere.

Usage

Run the CLI

# Using the bin script
./bin/run.js [COMMAND]

# Or if linked globally
cloudable [COMMAND]

Available Commands

# Show help
cloudable --help

# Show version
cloudable --version

# Run the hello command
cloudable hello
cloudable hello world
cloudable hello --name=YourName

Development

Project Structure

cloudable/
�� bin/                    # Entry point scripts
   �� dev.js             # Development mode (with ts-node)
   �� run.js             # Production mode
�� src/                   # TypeScript source files
   �� commands/          # CLI commands
       �� hello.ts       # Example command
�� dist/                  # Compiled JavaScript (generated)
�� tsconfig.json          # TypeScript configuration
�� package.json          # Project metadata and dependencies

Development Workflow

  1. Make changes to files in src/

  2. Run in development mode (auto-compiles TypeScript):

    npm run dev [COMMAND]
    # or
    ./bin/dev.js [COMMAND]
  3. Build for production:

    npm run build
  4. Run production build:

    npm run start [COMMAND]
    # or
    ./bin/run.js [COMMAND]

Adding a New Command

Option 1: Using oclif generator

npx oclif generate command mycommand

Option 2: Manual creation

Create a new file in src/commands/:

// src/commands/mycommand.ts
import {Args, Command, Flags} from '@oclif/core'

export default class MyCommand extends Command {
  static description = 'Description of your command'

  static examples = [
    '<%= config.bin %> <%= command.id %>',
  ]

  static flags = {
    force: Flags.boolean({char: 'f', description: 'Force the operation'}),
    name: Flags.string({char: 'n', description: 'Name parameter'}),
  }

  static args = {
    file: Args.string({description: 'File to process', required: true}),
  }

  async run(): Promise<void> {
    const {args, flags} = await this.parse(MyCommand)

    this.log(`Processing ${args.file}`)
    if (flags.force) {
      this.log('Forced mode enabled')
    }
  }
}

Then build and run:

npm run build
./bin/run.js mycommand --help

Creating Nested Commands (Topics)

Organize related commands by creating subdirectories:

Adding Tests

Create test files alongside your commands:

# Install testing dependencies
npm install --save-dev @oclif/test mocha chai

# Create test file
mkdir -p test/commands
touch test/commands/mycommand.test.ts

Example test:

import {expect, test} from '@oclif/test'

describe('mycommand', () => {
  test
    .stdout()
    .command(['mycommand', 'file.txt'])
    .it('runs mycommand', ctx => {
      expect(ctx.stdout).to.contain('Processing file.txt')
    })
})

Configuration

The CLI configuration is in package.json under the oclif key:

{
  "oclif": {
    "bin": "cloudable",
    "commands": "./dist/commands",
    "dirname": "cloudable",
    "topicSeparator": " "
  }
}

Scripts

  • npm run build - Compile TypeScript to JavaScript
  • npm run dev - Run CLI in development mode
  • npm run start - Run compiled CLI
  • npm test - Run tests (when configured)

Resources

Contributing

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature/my-feature
  3. Make your changes and commit: git commit -am 'Add new feature'
  4. Push to the branch: git push origin feature/my-feature
  5. Submit a pull request

License

ISC

Issues

Report issues at: https://github.com/Jai-Dhiman/cloudable/issues