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

@greatstore/cli

v0.0.32

Published

CLI for administering GreatStore stores and authoring custom components.

Readme

@greatstore/cli

Administer your GreatStore from the command line — store configuration, MCP connectors, and custom in-chat apps — and set up your AI coding agent to build with GreatStore.

npm install -g @greatstore/cli
gs skill                  # teach your AI coding agent to build with GreatStore
gs login
gs configure              # see your store's configuration
gs apps init --store <slug>
cd <project> && npm install
gs apps init my-widget
gs apps build
gs apps push
gs apps publish my-widget

The CLI mirrors the admin dashboard: gs configure, gs connectors, and gs apps correspond to the Configure, Connectors, and Apps panels, with the same field names and behaviour.

Commands

Account

| Command | What it does | | ----------- | --------------------------------------- | | gs login | Sign in. | | gs logout | Sign out. | | gs whoami | Print the identity you're signed in as. |

Configure

| Command | What it does | | ---------------------------------------- | ---------------------------------------------------------- | | gs configure [--json] | Show the store configuration. | | gs configure set --<field> <value> | Edit it. Same fields as the dashboard: --displayName, --assistantName, --salesGuide (or --salesGuideFile <path>), --storeLink, --extraOrigins a,b, --shopifyLoginGate true\|false, --theme '<json>' (or --themeFile <path>), --cspScriptHosts a,b, --cspConnectHosts a,b. Pass "" to clear a field. | | gs configure upload <kind> <file> | Upload icon, logoLight, or logoDark (.png/.jpg/.webp). | | gs configure clear <kind> | Remove an uploaded asset. |

Connectors

| Command | What it does | | ------------------------------------------------------------ | ------------------------------------------------------ | | gs connectors [--json] | List the Maker MCP toggle and custom MCP connectors. | | gs connectors add <name> --url <url> [--token <t>] [--profileUrl <u>] [--disabled] [--force] | Add a connector. It's probed for tool discovery first; --force saves it anyway. | | gs connectors remove <name\|id> | Delete a connector. | | gs connectors enable\|disable <name\|id> | Toggle a connector without deleting it. | | gs connectors maker on\|off | Toggle the Maker MCP. | | gs connectors health [<name\|id>] [--json] | Live-probe saved connectors. |

Apps

Custom in-chat app (remote component) commands. Each also works at the top level (gs push == gs apps push), so existing scripts keep working.

| Command | What it does | | ------------------------------------------------------ | -------------------------------------------------- | | gs apps init <name> [--out <dir>] [--store <s>] | Scaffold a working component project. | | gs apps build [<name>] | Build component bundle(s); no args = all. | | gs apps list [--json] | List components in the current store. | | gs apps pull <name> [--draft\|--live\|--version N] [-o <dir>] | Download a component to disk. | | gs apps push [<name>] [--manifest path] [--bundle path] | Upload local changes. | | gs apps publish <name> [--version N] | Ship a component (optionally a previous version). | | gs apps unpublish <name> | Hide a published component. | | gs apps delete <name> [--yes] | Remove the component. |

Agent skill

| Command | What it does | | ------------------------------------ | --------------------------------------------------------- | | gs skill [--global] [--dir <path>] | Install the GreatStore agent skill for AI coding agents. |

Agent skill

gs skill installs the GreatStore agent skill — a guide AI coding agents (Claude Code and friends) use to build with GreatStore: AI content for your own UI, chat entry points, page tools the assistant can call, custom in-chat components, push notifications, and the store's MCP endpoints.

gs skill             # → ./.claude/skills/greatstore/  (this project)
gs skill --global    # → ~/.claude/skills/greatstore/  (every project)
gs skill --dir <p>   # → <p>/greatstore/               (custom location)

Run it again any time to update an installed copy. No sign-in or store needed.

Store selection

Every command except login, logout, whoami, and skill needs a store.

  • App commands read the slug from a .gsrc in the current directory or any ancestor: {"store":"demo"}. gs apps init --store <slug> writes it for you, so commands inside a scaffolded project don't need a flag.
  • Admin commands (configure, connectors) also accept --store <slug> directly, so they work outside a scaffolded project.