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

@vlandoss/vland

v0.3.1

Published

The CLI to init a new project in Variable Land

Readme

🦉 vland

The CLI to init a new project in Variable Land

Prerequisites

  • Node.js >= 20.0.0

Installation

Run it directly with npx:

npx @vlandoss/vland init

…or install it globally:

pnpm add -g @vlandoss/vland
vland init

Usage

vland init                        # interactive
vland init my-app -t library      # explicit template
vland init my-app -t backend --no-install --no-git

See CLI.md for the full reference (auto-generated per release).

Templates

| Template | What you get | | ---------- | ----------------------------------------------------------------------------------------- | | library | A standalone TypeScript library with Vitest + Changesets release workflow. | | backend | An Elysia (@elysiajs/node) backend with evlog, Vitest, Dockerfile, CI shape. | | monorepo | pnpm + Turbo workspace with an Elysia API, a Vite-React SPA, and a few internal packages. |

All templates target Node.js, use pnpm, and ship @rrlab/cli (rr) as the single entry point for lint, format, type-check, and build. The per-tool config files (biome.json, tsconfig.json, tsdown.config.ts) are not bundled — run rr plugins add biome ts tsdown (one at a time) in your new project to opt in. See the scaffolded README for the exact post-install setup.

Shell completion

vland ships a completion subcommand that prints a shell-specific script. Add it to your shell rc file:

# zsh — ~/.zshrc
eval "$(vland completion zsh)"

# bash — ~/.bashrc
eval "$(vland completion bash)"

# fish — ~/.config/fish/config.fish
vland completion fish | source

Prerequisite: the usage CLI must be on your PATH (it powers completion at runtime). Install via one of:

mise use -g usage
brew install usage

When you upgrade @vlandoss/vland, the next shell session will pick up new commands automatically — no need to re-run anything.

Troubleshooting

To enable debug mode, set the DEBUG environment variable to vland:* before running any command.

DEBUG=vland:* vland init my-app

To point init at local templates instead of fetching from GitHub (useful when developing inside this monorepo):

VLAND_TEMPLATES_DIR=/absolute/path/to/dx/vland/templates vland init my-app -t library