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

@octaviaflow/cli

v3.0.18

Published

CLI for OctaviaFlow Design System

Readme

@octaviaflow/cli

Command-line companion for the OctaviaFlow Design System. Scaffolds projects, adds components, validates config, and sets up @octaviaflow/logger.

Installation

The CLI is usually invoked via npx, but can also be installed locally:

npm install -D @octaviaflow/cli

Binary: ods.

Requires Node.js >= 22.

Commands

ods init                      Initialize OctaviaFlow in your project
ods add <component...>        Add components to your project
ods generate                  Generate token files from config
ods check                     Validate your OctaviaFlow config
ods upgrade                   Upgrade OctaviaFlow packages
ods scaffold <type> <name>    Scaffold a component, plugin, or tool  (alias: new)
ods logger <verb>             Manage @octaviaflow/logger  (verbs: init, doctor, test)

Global flags: --help, --version.

ods logger — Logger setup

A dedicated namespace for installing and configuring @octaviaflow/logger without touching the rest of the design system. Runs standalone — it doesn't pull in UI tokens or component presets.

ods logger init

Interactive setup. Detects the project's framework (Next.js, Vite, Express, etc.) and writes a logger.config.ts tailored to your answers.

Prompts cover:

  • Service typebackend, engine, worker, scheduler, or ui.
  • Runtime modedevelopment, staging, or production.
  • Log level and formatinfo/debug/warn/trace and json/pretty/compact/ecs.
  • Targets (multiselect)console, file, s3, gdrive, onedrive, dropbox. Disabled targets are written into the config commented-out so they're easy to turn on later.
  • Per-target specifics — bucket + region + prefix for S3, folderId for Google Drive, folder paths for OneDrive and Dropbox.
  • Retention preset — Standard (10 MB × 10 files × 30 days), Lean (1 MB × 5 × 7), Generous (50 MB × 30 × 90), or Custom.

Side effects (all optional, confirmed inline):

  • Writes logger.config.ts (default path; override via --config <path>).
  • Writes src/logger.ts bootstrap that calls createLoggerFromConfig(config).
  • Appends logs/ to .gitignore if not already present.
  • Installs @octaviaflow/logger via npm (skip with --no-install).

Credentials for cloud targets are never written to logger.config.ts. The config references env var names only — the transport reads the values from process.env at construction time.

Flags:

  • --config <path> — explicit config file path (default: ./logger.config.ts).
  • --no-install — skip the npm install step.

ods logger doctor

Non-interactive audit. Useful on CI or pre-deploy.

  • Resolves logger.config.{ts,mjs,js,json} in cwd.
  • Parses the file (via dynamic import() or JSON.parse).
  • Runs validateLoggerFileConfig from @octaviaflow/logger/config and reports every issue — warnings and errors both.
  • For each enabled cloud target, checks that its required env vars are set in process.env.
  • For the file target, probes that the log directory exists and is writable (via mkdir + write + unlink).

Exits 0 on clean, 0 with message on warnings, 1 on errors.

Flag: --config <path>.

ods logger test

End-to-end smoke test. Emits one line at each level (trace, debug, info, warn, error) through every configured transport, then flushes and closes. For cloud transports this also triggers the retention sweep.

Flag: --config <path>.

Development

npm run build      # tsup dual ESM+CJS
npm run test       # vitest
npm run lint       # biome

License

Apache-2.0