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

akai-cli

v0.2.1

Published

CLI tool for managing the Akai engine in Docker

Readme

Akai CLI

CLI tool for managing the Akai engine in Docker. Built with TypeScript, this tool provides a simple interface to set up, manage, and monitor Docker containers running the Akai engine.

🚀 Features

  • TypeScript-based: 100% TypeScript source code
  • Visual CLI: Beautiful output with colors, spinners, and boxed messages
  • Docker Management: Easy setup and management of Docker containers
  • Service Support: Extensible architecture for multiple services
  • Idempotent Operations: Safe to run multiple times

📋 Prerequisites

  • Node.js >= 14.0.0
  • Docker installed and running
  • npm or yarn

🛠️ Development

Install Dependencies

npm install

Build the Project

Compiles TypeScript to JavaScript in the dist/ folder:

npm run build

Local Testing

To test the CLI locally without publishing:

  1. Build the project:

    npm run build
  2. Link globally (for development):

    npm link

    This creates a global symbolic link that allows you to use the akai command from anywhere.

  3. Test the commands:

    akai help
    akai setup
    akai status
    akai restart
  4. Unlink (when you're done testing):

    npm unlink -g akai-cli

Run Directly (without linking)

You can also run the CLI directly without linking:

npm start
# or
node dist/index.js help

Development with Watch Mode

For continuous development, you can use tsc in watch mode:

npx tsc --watch

In another terminal, run the CLI after each change:

npm start

📦 Publishing

Preparation for Publishing

  1. Verify everything is built:

    npm run build
  2. Check git status:

    git status
  3. Update the version:

    Edit package.json and update the version field following Semantic Versioning:

    • MAJOR.MINOR.PATCH (e.g., 0.1.00.2.0 for new features)
    • Or use npm version:
      npm version patch  # 0.0.1 → 0.0.2
      npm version minor  # 0.0.1 → 0.1.0
      npm version major  # 0.0.1 → 1.0.0
  4. Verify required files are included:

    Make sure these files/directories are in the repository:

    • dist/ (compiled code)
    • dockerfiles/ (static Dockerfiles)
    • package.json
    • README.md

Publish to npm

  1. Login to npm (if first time):

    npm login
  2. Verify you're authenticated:

    npm whoami
  3. Publish:

    npm publish

    To publish as public (if scope is private):

    npm publish --access public
  4. Verify the publication:

    npm view akai-cli

Publish a Beta/Pre-release Version

npm version prerelease --preid=beta
npm publish --tag beta

Users can install with:

npm install -g akai-cli@beta

Update After Publishing

  1. Commit and push changes:
    git add .
    git commit -m "chore: bump version to X.X.X"
    git push
    git push --tags  # If you used npm version

📝 Available Commands

Once installed (globally or linked), you can use:

akai help              # Show help
akai setup             # Initial setup
akai setup --service <name>  # Setup with custom service
akai status             # Container status
akai status --service <name>  # Status with custom service
akai restart            # Restart container
akai restart --service <name>  # Restart with custom service

🏗️ Project Structure

akai-cli/
├── dockerfiles/           # Static Dockerfiles per service
│   └── akai-engine/
│       └── Dockerfile
├── src/                   # TypeScript source code
│   ├── commands/          # CLI commands
│   ├── config/           # Configuration and constants
│   ├── services/         # Services (Docker, Git)
│   ├── utils/            # Utilities (Output)
│   └── index.ts          # Entry point
├── dist/                  # Compiled code (generated)
├── package.json
├── tsconfig.json
└── README.md

🔧 Available Scripts

  • npm run build - Compile TypeScript to JavaScript
  • npm start - Run the compiled CLI
  • npm test - Run tests (placeholder)
  • npm run lint - Run linter (placeholder)

📚 Resources

🤝 Contributing

  1. Fork the project
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Commit your changes (git commit -m 'feat: Add some AmazingFeature')
  4. Push to the branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

📄 License

ISC