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

@cvhome-saas/lcl

v0.1.0

Published

Run, supervise, inspect, and port-shift complex local microservice stacks from one lcl.yml.

Readme

lcl

lcl runs a complex local stack from one lcl.yml. It allocates a stable set of ports, starts dependencies in readiness order, supervises foreground processes, manages optional Docker Compose infrastructure, and keeps logs and state for several named stacks at once.

The runner is language-neutral. If a service can be launched as a foreground command, lcl can supervise it.

Install

Node.js 22 or newer is required. macOS, Linux, and WSL2 are supported.

npm install -g @cvhome-saas/lcl
lcl --version

Create a starter configuration:

lcl init --template empty
# also available: node, python, java, compose
lcl validate

lcl init adds .lcl/ to .gitignore. The only project configuration owned by the CLI is lcl.yml; runtime state stays under .lcl/<stack>/.

A small stack

version: 1
name: shop

ports:
  step: 1000

compose:
  files: [compose.yml]
  default: [postgres]

services:
  catalog:
    cwd: services/catalog
    command: [python, -m, uvicorn, app:app, --port, "${port.catalog.http}"]
    depends-on: [postgres]
    ports:
      http: 8080
    health:
      type: http
      port: http
      path: /health

  storefront:
    cwd: apps/storefront
    prepare:
      - [npm, run, build:libs]
    command: [npm, run, dev, "--", --port, "${port.storefront.http}"]
    depends-on: [catalog]
    ports:
      http: 3000
    environment:
      CATALOG_URL: "http://localhost:${port.catalog.http}"
    health:
      type: http
      port: http
      path: /

urls:
  - { label: storefront, url: "http://localhost:${port.storefront.http}" }
lcl start -d                         # start everything and return when ready
lcl start storefront -d              # also starts catalog and postgres
lcl status
lcl urls
lcl logs catalog -f
lcl why catalog
lcl restart catalog
lcl stop

Generic service contract

Each entry in services is a foreground process:

| Key | Meaning | |---|---| | command | Argument array executed without a shell. Preferred because quoting is unambiguous. | | shell | Explicit POSIX shell command for pipelines or shell expansion. Mutually exclusive with command. | | cwd | Working directory relative to lcl.yml. Defaults to the configuration directory. | | prepare | Commands run to completion before each service start. Entries may be argv arrays or command objects. | | depends-on | Source or Compose services that must be ready first. Transitive dependencies start automatically. | | ports | Any number of named TCP ports. All are shifted together when the configured sequence is occupied. | | environment | Environment values, with variable interpolation. | | health | http, tcp, log, or process; defaults to TCP for a service with ports and process-alive otherwise. |

Examples for common ecosystems use the same fields:

services:
  spring:
    command: [./gradlew, :api:bootRun, "--args=--server.port=${port.spring.http}"]
    ports: { http: 8080 }

  maven:
    command: [./mvnw, -pl, billing, spring-boot:run, "-Dspring-boot.run.arguments=--server.port=${port.maven.http}"]
    ports: { http: 8081 }

  go:
    command: [go, run, ./cmd/api]
    environment: { PORT: "${port.go.http}" }
    ports: { http: 8082 }

  rust:
    command: [cargo, run, --bin, worker]
    environment: { PORT: "${port.rust.http}" }
    ports: { http: 8083 }

  worker:
    command: [python, worker.py]
    health: { type: log, ready-log: "worker ready", timeout: 30 }

Portless workers, file watchers, tunnels, webhook listeners, and similar tools are supervised like servers. They can reference the complete allocated port map, but should not declare a port unless they actually listen on it. See the runnable examples/long-running-tools example for log readiness, dependency ordering, cross-service forwarding, and automatic .env injection.

The complete configuration contract is schema/lcl.schema.json. Unknown keys and invalid combinations fail during lcl validate, before any process or container is started.

Named stacks and ports

The configured ports are used when available. If one is occupied, the whole stack moves by ports.step until every declared source port and selected Compose port is free.

lcl start -d
lcl start -d --stack feature-x
lcl ports --stack feature-x
lcl urls --stack feature-x
lcl stop --stack feature-x

Useful policies:

  • --ports configured: require the configured ports and fail on a collision.
  • --ports shift: always start at the first shifted sequence.
  • --ports offset=2: force 2 × ports.step.
  • ports.skip-configured: true: make shifted ports the project default.

Variables available in commands, environment, hooks, generated files, and URLs include:

  • ${stack}, ${stack.dir}, ${root}, ${project}, ${offset}, ${service}, ${port}
  • ${port.<service>.<name>} for source services
  • ${port.<compose-service>.<container-port>} for Compose services
  • ${env.NAME} for an environment value supplied to the lcl process

Every assigned port is also exported as an uppercase LCL_PORT_* environment variable. lcl ports --env prints the exact variables and resolved URLs for shell use.

Project .env

If a .env file exists beside lcl.yml, LCL parses it with Node's dotenv rules and injects its values as defaults into source services, prepare commands, the optional build command, and hooks. This supports programs that do not load dotenv files themselves. No configuration field is required.

Existing host variables override .env; generated LCL_* variables and explicit global or service environment values override both. ${env.NAME} remains an explicit lookup of the environment supplied to the lcl process. LCL does not expand variable references inside .env, and Compose environment remains controlled by Compose and compose.environment. A running supervisor keeps the values loaded at stack start, so stop and start the stack to reload changes. Because lcl why shows resolved diagnostics, do not treat .env values as hidden output.

Docker Compose

Compose is optional. When configured, lcl asks docker compose config for the canonical service and port model, creates a per-stack port override, and uses an isolated project name. Containers with health checks wait for healthy; other containers wait for their published ports.

compose:
  files: [compose.yml, compose.local.yml]
  default: [postgres, redis]
  environment:
    POSTGRES_TAG: 17-alpine

Use --infra all, --infra postgres,redis, or --no-infra to override the default. lcl stop --hard also removes volumes belonging to that exact Compose project.

Commands

lcl start [service...] [-d] [--build] [--parallel N] [--fail-fast]
lcl stop [service...] [--hard]
lcl restart [service...]
lcl status [--json]
lcl urls
lcl ports [--json|--env]
lcl logs [service...] [-f] [-n N] [--since 10m] [--grep REGEX] [--errors]
lcl events [-f] [--since 1h] [--service NAME] [--json]
lcl why SERVICE
lcl doctor
lcl validate [--json]
lcl list
lcl clean [--all]

lcl only signals process groups it launched and can identify. A stale recorded port owned by another process is reported, never killed. Foreground programs should not daemonize themselves.

Development

npm install
npm run check
npm test
npm pack --dry-run

CI tests Node.js 22 and 24 on Ubuntu and macOS. Docker-backed Compose tests run on Ubuntu. See CONTRIBUTING.md for the release workflow.

License

Apache License 2.0.