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

@omg-dev/apps

v0.4.45

Published

Retired create/deploy CLI for omg apps. The current product is the local control plane in BennyKok/omg.dev.

Readme

@omg-dev/apps

Retired create/deploy CLI. It can still create a starter and publish an app to https://<slug>.omgs.app. That is not the current product.

The current product is the local agent control plane in BennyKok/omg.dev:

curl -fsSL https://raw.githubusercontent.com/BennyKok/omg.dev/main/scripts/setup.sh | bash

Then open http://localhost:8766. You bring your own agent accounts.

This package used to publish as @omg-dev/cli 0.4.x. That name now belongs to BennyKok/omg.dev at 0.5.0+. This repository must never publish @omg-dev/cli again. The binary is omg-apps so it cannot collide with the control-plane omg command.

lfg remains a compatibility alias for the control-plane command. It is not a second product.

Install

npm install --global @omg-dev/apps
omg-apps help

Create a starter with omg-apps create my-app, or with npx create-omg my-app. create-omg is also not the current product.

Commands

| Command | Does | | -------------------------------------------------- | ---------------------------------------------------------------- | | omg-apps create <name> [--no-install] | Create an app from the official starter. | | omg-apps login | Sign in through the browser with OAuth 2.1 + PKCE. | | omg-apps login --token "$OMG_API_KEY" | Save an API key for headless use. | | omg-apps whoami | Print the authenticated account without printing its credential. | | omg-apps logout | Remove saved credentials. | | omg-apps apps | List apps visible to the authenticated account. | | omg-apps connect [--new] [--no-install] | Pair this machine with the hosted relay. | | omg-apps deploy [--name X] [--dir .] [--no-wait] | Upload source, build, and publish. | | omg-apps status [--dir .] | Show deploy status for the linked directory. | | omg-apps link <slug> [--dir .] | Link a directory to an app on the account. | | omg-apps dev [--dir .] [--agent-port N] | Run the project with local VM-service emulation. |

Hosted pairing (login / connect) stays in this repository. It is not the first-run path. First run is the BennyKok/omg.dev setup script.

Deploy writes a pending operation key to .omg/project.json before it uploads source. If the response is lost, the next identical deploy reuses that key and the control plane returns the original project and run instead of creating a second app.

Releasing

packages/cli/scripts/release.sh            # patch bump; minor|major also accepted
packages/cli/scripts/release.sh --dry-run  # build, verify, pack, publish nothing

This publishes @omg-dev/apps only. The script refuses to publish @omg-dev/cli or a binary named omg.