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

@callcorpacd/buildcc

v0.1.1

Published

Install and run the CallCorp BuildCC CLI (downloads self-contained binary from the public channel)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

bentonsmithbentonsmithdavid.petersondavid.petersonshanekellyshanekelly

Keywords

Readme

@callcorpacd/buildcc

Thin npm wrapper that installs and runs the BuildCC self-contained CLI from the VuePortal Downloads channel.

Install

npm install -g @callcorpacd/buildcc
buildcc --init

Or without a global install:

npx @callcorpacd/buildcc --help

Defaults are lab until production Downloads are ready:

| Role | Default | |------|---------| | Portal (download binary / channel) | portal.callcorplab.com | | API (--init login) | api.callcorplab.com |

Channel / host overrides

Channel URL resolution:

  1. BUILDCC_CHANNEL_URL (full URL)
  2. BUILDCC_PORTAL_HOST → https://{host}/Downloads/BuildCC/channel.json
  3. BUILDCC_DOMAIN → portal host from domain map
  4. Persisted install-state.json ChannelUrl
  5. Baked default (portal.callcorplab.com)

--init API host resolution:

  1. --host
  2. BUILDCC_API_HOST
  3. BUILDCC_DOMAIN → api host
  4. Baked default (api.callcorplab.com)

Domain map

| BUILDCC_DOMAIN | Portal | API | |------------------|--------|-----| | callcorplab.com (default) | portal.callcorplab.com | api.callcorplab.com | | callcorp.com or total.care | portal.total.care | api.callcorp.com | | other (e.g. widgets.com) | portal.{domain} | api.{domain} |

# Production
BUILDCC_DOMAIN=callcorp.com buildcc --init

# Partner
BUILDCC_DOMAIN=widgets.com buildcc --init

# Explicit hosts
BUILDCC_PORTAL_HOST=portal.widgets.com BUILDCC_API_HOST=api.widgets.com buildcc --init

Changing portal/domain via env when an older channel is already installed re-downloads the binary.

On first run the resolved channel URL is written to install-state.json so BuildCC auto-update works without the env var.

Publish bake

# lab (default)
npm publish

# production-flavored pack
BUILDCC_DOMAIN=callcorp.com npm pack

Cache / install location

| OS | Path | |----|------| | Windows | %LOCALAPPDATA%\CallCorp\BuildCC\ | | Linux / macOS | ~/.local/share/CallCorp/BuildCC/ |

Binary: current/BuildCC(.exe).