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

jervis-installing-cli

v0.1.0

Published

Jervis Installing CLI — use `jv i` or `jv install` to sync any project.

Readme

jervis-installing-cli

Jervis Installing CLI — polyglot project bootstrap in one command.

Detects your ecosystem (Node, PHP, Python, Ruby, Go, Rust, .NET, Java, Dart/Flutter, Elixir, Makefile) and runs the right install → migrate → optimize sequence for the current project and any linked projects.

Install

npm i -g jervis-installing-cli
jv --version
jervis --version

Main Commands

# Full bootstrap (pull → install → migrate → optimize)
jv i
jv install
jervis i
jervis install

# Dependencies only
jv deps

# Health and plan check
jv doctor
jv doctor --json

# Link a frontend ↔ backend project
jv link ../my-frontend

# Start app services
jv start
jv link start

# Branch workflows
jv branch
jv branch develop
jv link branch
jv link branch develop

# Migrations and optimization
jv migrate
jv optimize

# Pull only
jv pull

# Git post-merge hook
jv hook install

Flags

| Flag | Effect | | --------------- | ---------------------------------------------- | | --cwd <path> | Run against a different directory | | --json | Emit structured JSON events (machine-readable) | | --linked | Include linked projects for root-scoped verbs | | --linked-only | Run on linked projects only | | --no-linked | Force current-project-only execution |

Notes

  • jv branch with no argument opens interactive branch selection.
  • jv link branch targets linked projects only.
  • jv i and jv install run the full sync flow (pull → install → migrate → optimize).
  • jv deps keeps install-only behavior without migrate/optimize.
  • Legacy aliases (switch, link switch branch) are still accepted.
  • If a required ecosystem tool is missing, the step is skipped gracefully.

License

MIT