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

@grove-sh/cli

v0.8.0

Published

Local HTTPS hostnames, ports, and env vars, scoped per git worktree

Readme


You probably have a feature you're working on, a PR you promised to review, and an agent or two grinding away on branches of their own, sometimes in a different repo. Nothing stops you running all of that at once. Nothing coordinates it either. You pick ports by hand, you edit .env in each checkout, and you swear you'll put it all back afterwards. So mostly you stop one thing to look at another.

Grove uses worktrees to keep contexts separate. Every worktree of every repo on your machine is a context, and each one gets its own hostname, its own ports, and its own env vars. One daemon serves them all, so run as many worktrees on as many projects as you like and they won't collide:

~/code/app            https://app.grov.site        web:20107   db:20402
~/worktrees/app/feat  https://app-feat.grov.site   web:20871   db:20533
~/code/shop           https://shop.grov.site       web:20334   db:20118

No port in the URL, a certificate your browser actually trusts, and one command to run anything inside that context:

grove exec -- vite dev

There's nothing to configure per worktree. Ports come from a hash of the worktree and the thing being served, so a fresh checkout is addressable the moment it exists and leaves nothing behind when you delete it. And since the worktree's name is a value you can template, {context.slug} in a database URL points each one at its own database on the postgres you're already running.

Documentation

You can read the documentation here.

Quickstart

npm install -g @grove-sh/cli
grove install            # once per machine
grove init               # once per project, writes grove.toml
grove exec -- vite dev

This package is a wrapper. It installs the binary for your platform and runs it.

grove install is a separate step on purpose. It generates a certificate authority and adds it to your trust stores, and it prints the one privileged step your platform needs, running it only when you say so. Neither belongs in an npm install that nobody is watching.

Why not lando or ddev?

You could describe grove as "lando, but bring your own services". That's close, but it undersells the part that matters.

lando and ddev get a lot right. You get a real hostname like app.lndo.site or app.ddev.site, https with a certificate your browser trusts, and a stack that comes up with one command. Grove keeps all of that.

What they assume, along with docker compose, is that the project is the unit. One checkout, one hostname, one set of ports. Clone the same project a second time and it collides with the first until you rename it and hand-edit the config. Their answer is to wrap everything in containers, which does isolate your services. Unfortunately it isolates your tooling right along with them, and you're still stuck at one checkout per project.

Grove takes a different approach.

A context is a worktree. Hostnames, ports, and env vars are derived from the worktree, not written down. A fresh checkout serves on its own name with no setup, and five checkouts are no harder than one. That holds across repos too, so nothing defaults to 3000 twice. Run several agents at once and each has its own stack to check its work against.

Bring your own services and namespace them. Grove doesn't run postgres or redis. It addresses the ones you already run and gives each worktree its own slice. {context.slug} in a connection string is a database per worktree on one server. The service is shared; the data isn't.

Your tooling stays on your host. pnpm dev runs as you, with your node and your files. Hot reload watches the real filesystem, your debugger attaches, and the paths in your editor are the paths the process sees. No VM to feed, no bind mount to wait on.

Real hostnames, real HTTPS. A wildcard certificate from a root your machine trusts, and real DNS under grov.site. No hosts file, no port in the URL, and secure cookies and OAuth redirects behave like production. Two branches are two origins, so they never share a session. localhost:3000 and localhost:3001 do, because cookies don't care about ports.

Adopting it isn't a team decision. Under CI grove steps aside and runs your command untouched, and --if-available asks for the same anywhere. A teammate who never ran grove install runs the same scripts. Your lando project keeps working too.

| | lando, ddev | docker compose | grove | |-----------------------------|------------------------|----------------|---------------------| | The unit | project | project | worktree | | Runs your services | yes | yes | no, addresses yours | | Where your tooling runs | container | container | your host | | Several checkouts at once | rename and reconfigure | juggle ports | nothing to do | | Needed in CI | yes | yes | no |

What grove asks of your project

Your services have to be namespaceable. A database per worktree works because postgres has databases. A single-tenant listener like the Stripe webhook forwarder doesn't multiply, however nicely you ask. Each worktree's database also needs its own migrations and seed, which is a chore grove creates and does nothing about. Last, your dev server has to bind the port it's handed. Next.js reads PORT on its own, Vite has to be told, and a server that picks its own port is one grove can't reach. That catches nearly everyone, so it has a page of its own.