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

@queelabs/cli

v0.0.2

Published

CLI for operating Quee marketplace environments

Readme

@queelabs/cli

CLI for bootstrapping and operating Quee marketplace environments.

Quee: https://quee.one

Install

npm install -g @queelabs/cli

Or run without a global install:

npx -y @queelabs/cli@latest init

quee init

quee init creates or connects a marketplace, can configure payment + settlement rails, writes local config to .quee/config.json, and prints the env block your app needs.

Interactive init now does the following:

  • checks for an existing .quee/config.json and asks before reinitializing
  • uses arrow-key prompts instead of numeric menus
  • lets you multi-select checkout rails with Space + Enter
  • creates a marketplace using POST /v1/internal/setup-marketplace when QUEE_MANAGEMENT_TOKEN is set, otherwise falls back to public bootstrap
  • installs only the connector packages that match the rails you selected, with a quiet progress UI instead of dumping install logs on success
  • stores rail credentials in Quee via PUT /v1/marketplaces/:id/rails/:railType so the API can keep encrypted config at rest
  • adds .quee to .gitignore automatically when saving local config

Payment rail behavior:

  • one selected rail: mpp is configured directly as that adapter
  • multiple selected rails: mpp is configured as an umbrella orchestrator and each selected rail is stored separately for checkout
  • settlement still defaults to Tempo native, with http, log, or skip available

Default targets:

  • Local Dev for development traffic
  • Hosted (quee.one) for real traffic
  • Self-hosted for your own deployment

Direct flags:

quee init --local
quee init --hosted
quee init --self-hosted
quee init --url https://api.example.com

If --marketplace and --key are provided, init connects an existing marketplace instead of creating a new one.

Hosted URL defaults

The CLI can auto-resolve hosted targets from environment variables:

QUEE_HOSTED_PROD_API_URL=https://api.example.com
QUEE_HOSTED_SANDBOX_API_URL=https://sandbox-api.example.com

Fallback names:

  • QUEE_HOSTED_API_URL or QUEE_DEFAULT_API_URL for hosted production
  • QUEE_SANDBOX_API_URL for hosted sandbox

Local Dev prefers the hosted sandbox URL when it is configured. If no sandbox URL is set, it falls back to http://localhost:3001.

If these are not set, the CLI will prompt for the URL once and save it in .quee/config.json.

Recommended hosted model

If you operate Quee for customers, use separate environments:

  • production API + production database
  • sandbox API + sandbox database

That keeps dev/test orders, receipts, and settlements out of production state.

Other commands

quee db-check
quee reconcile
quee drain-webhooks

Run quee --help for the full command list.