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

code0

v1.0.10

Published

Code0 CLI

Readme

code0 CLI

This module is a CLI designed for managing operations related to code0. It is written in Deno, and currently, you can run it using Deno or install the binary globally using one of the methods described in the installation section.

Please note that running with npx is not supported at the moment. The intention is to build the binaries and publish them to npm so that the Node.js binary can be spawned as a child process.

If Deno is not a suitable approach for this use case, we can consider using node Cliffy, this module can be easily ported to cliffy.

NOTE: This CLI is compatible with the new database/api implementation only.

Why?

The code0 CLI offers a quick and efficient method to incorporate a generated component into your project. This concept draws inspiration from npx v0 add, a tool designed to streamline the process of copying, creating files, and pasting code from a web client. Additionally, it proves beneficial when operating or consuming an instance from a remote origin.

Run

To execute the CLI directly, you can use the following command:

deno run -A https://code0-run.deno.dev

Please note that "code0-run.deno.dev" is a temporary domain.

Install

Using Deno

You can install the CLI using Deno with the following command:

deno install -A -n code0 -f https://code0-run.deno.dev

System-wide Installation

| Platform | Command | |----------|---------------------------------------------------------| | Windows | iwr instl.sh/denyncrawford/code0/windows \| iex | | Linux | curl -sSL instl.sh/denyncrawford/code0/linux \| bash | | macOS | curl -sSL instl.sh/denyncrawford/code0/macos \| bash |

Usage

Installing code0 Locally

To install code0 locally or if you haven't installed it yet, you can use the following command:

code0 install

Arguments

  • [destination]: Specify the name of the destination folder. By default, it installs it in /code0-main.

Setting the Server

Since code0 doesn't have an official host, you need to set an code0 server to make it work (usually http://localhost:3000):

Please note that code0 server must be running on cli operations

code0 set "http://localhost:3000"

Getting a Component

You can add a generated component to your project by running:

code0 add <component_id> [iteration_version]

Arguments:

  • <component_id> (required): The actual name of your generated component.
  • [iteration_version] (optional): The specific iteration version to use. By default, it adds the latest iteration of the component.

Options

  • --directory (optional): Specify the component's destination directory. By default, it resolves to /components.

Example:

code0 add HelloWorldButton_i9n25 1695552737252

Please note that this documentation assumes that "code0-run.deno.dev" and related domain-specific details are temporary and subject to change based on upstreams.