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

inkstream-cli

v1.0.1

Published

CLI to sync project docs into a central Vercel-deployed docs site

Downloads

20

Readme

inkstream-cli

Sync project markdown docs into a central Vercel-deployed documentation site.

Installation

# Global install (recommended)
npm install -g inkstream-cli

# Or local install + link (for development)
cd inkstream-cli
npm install
npm run build
npm link

Quick Start

# 1. Initialize — set up global config and clone your docs repo
inkstream init

# 2. Create a workspace
inkstream workspace add personal --name "Personal"
inkstream workspace use personal

# 3. Register a project (run from inside the project)
cd ~/dev/personal/my-project
inkstream project init --workspace personal --slug my-project

# 4. Sync docs to the central repo
inkstream sync

# 5. Watch for changes and auto-sync
inkstream watch

Commands

inkstream init

Prompts for your docs repo git URL and local path, writes ~/.inkstream/config.json, and clones the docs repo.

inkstream workspace add <slug> --name "<Name>"

Creates a workspace config at ~/.inkstream/workspaces/<slug>.json and registers it globally.

inkstream workspace use <slug>

Sets the active workspace in global config.

inkstream workspace list

Lists all registered workspaces, highlighting the active one.

inkstream project init --workspace <slug> --slug <projectSlug> [--docs-root <path>] [--name <n>]

Registers the current git repository as a project under the specified workspace.
Appends the current machine's path to localPaths if the project is already registered.

inkstream project list --workspace <slug>

Lists all projects in a workspace.

inkstream sync [--dry-run]

Copies the project's docs/ folder into the central docs repo:

<docsRepo>/content/<workspace>/<project>/<category>/<slug>.md

Then commits and pushes. Use --dry-run to preview without changes.

inkstream watch

Watches <projectRoot>/docs/**/*.md and auto-syncs on a 2-second debounce. Long-running foreground process (Ctrl-C to stop).

inkstream status

Shows resolved workspace/project info and whether the docs repo is up to date.

inkstream open [--base <url>]

Opens your browser at the docs URL for the current project. Defaults to http://localhost:3000.

Config Files

~/.inkstream/config.json — GlobalConfig

{
  "docsRepo": {
    "gitUrl": "[email protected]:you/inkstream-docs.git",
    "localPath": "/Users/you/dev/inkstream-docs"
  },
  "currentWorkspace": "personal",
  "workspaces": [
    {
      "slug": "personal",
      "name": "Personal",
      "configPath": "/Users/you/.inkstream/workspaces/personal.json"
    }
  ]
}

~/.inkstream/workspaces/<slug>.json — WorkspaceConfig

{
  "slug": "personal",
  "name": "Personal",
  "projects": {
    "inkstream": {
      "name": "InkStream",
      "localPaths": ["/Users/you/dev/inkstream"],
      "docsRoot": "docs"
    }
  }
}

localPaths — Multi-machine support

Because you may work on multiple machines, localPaths is an array. Running inkstream project init again from a different machine appends the new path rather than replacing it. This lets the same project be recognized regardless of where it's cloned.

Project Docs Structure

Inside each registered project, create a docs/ folder (or custom docsRoot):

docs/
  architecture/
    high-level.md
    data-flow.md
  workflows/
    docs-pipeline.md
  api/
    auth.md
  decisions/
    2026-02-20-viewport-centering.md

This maps to URL paths like:

/personal/inkstream/architecture/high-level
/personal/inkstream/workflows/docs-pipeline

Development

npm run build    # Compile TypeScript → dist/
npm run dev      # Watch mode
npm test         # Run tests