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

@clily/core

v0.1.0

Published

A modern, ergonomic TypeScript CLI framework with Standard Schema validation

Readme

@clily/core

A modern, highly ergonomic TypeScript CLI framework for Node, Bun, and Deno-style runtimes. clily acts as a unified configuration and execution engine, merging CLI arguments, environment variables, and local/global configuration files into a Single Source of Truth (SSOT) validated by Standard Schema.

Features

  • Standard Schema validation — Use Valibot, Zod, ArkType, or any Standard Schema-compatible library
  • End-to-end type safety — Advanced generics auto-merge flags and args into handler parameters
  • Config resolution — Merges CLI args > env vars > config files > schema defaults via c12
  • Interactive fallback — Prompts for missing required fields in TTY via @clack/prompts
  • Subcommand tree — Nested commands with inherited global flags and per-child type inference
  • Shell completions — Generate Bash, Zsh, Fish, and PowerShell completion scripts
  • Injectable runtime boundary — Override argv, env, cwd, stdout, debug/error logging, and exit handling for tests or embedding

Install

vp add @clily/core

Quick Start

import { clily } from '@clily/core'
import * as v from 'valibot'

const cli = clily({
  name: 'mycli',
  version: '1.2.0',
  completion: true,
  flags: v.object({
    verbose: v.optional(v.boolean(), false),
    logLevel: v.optional(v.picklist(['info', 'debug', 'warn', 'error']), 'info'),
  }),
  handler: async (args) => {
    if (args.verbose) console.log('Verbose mode enabled')
  },
  children: {
    deploy: {
      description: 'Deploy the project',
      args: v.object({
        apiKey: v.string(),
        dryRun: v.optional(v.boolean(), false),
      }),
      handler: async (args) => {
        console.log(`Deploying with key: ${args.apiKey}`)
      },
    },
  },
})

await cli()

Public API

The root package intentionally exposes a narrow API surface:

  • clily
  • createRuntime
  • getExecutionEnvironment
  • ClilyCommandError

Public root-level types:

  • ClilyOptions
  • ClilyHooks
  • ClilyRuntime
  • ClilyExitRequest
  • CompletionConfig
  • CompletionShell
  • ExecutionEnvironment

Internal schema plumbing, help/completion builders, and generic helper types are intentionally not exported from the package root.

Examples

The monorepo includes separate example workspaces in examples/README.md that validate:

  • Valibot, Zod, and ArkType
  • zsh, bash, fish, and pwsh completions
  • Node, Bun, and Deno-style runtime flows
  • injected exit and output handling for embedding and tests

Development

cd packages/core
vp check
vp test --typecheck
vp pack
vp run validate:dist