LPM CLI

LPM CLI is a native package manager and development toolkit. It installs packages from npm, private npm-compatible registries, JSR, and LPM.dev Registry; it is not limited to packages hosted on lpm.dev.

lpm install

For an existing JavaScript project, that command reads package.json, resolves each dependency from its configured registry, and creates the project lockfile and install layout.

Install LPM CLI

npm install -g @lpm-registry/cli

Homebrew and standalone installers are also available. See Install LPM CLI for supported platforms and verification.

Use LPM.dev Registry

Sign in when you want to publish, install private packages, or use another hosted LPM.dev Registry feature:

lpm login
lpm install @lpm.dev/acme.private-utils

LPM CLI recognizes @lpm.dev/* as the LPM.dev Registry scope. Public npm packages continue to use npm, and scopes mapped in .npmrc continue to use their configured registries.

Publish the current package to LPM.dev Registry:

lpm publish

Every new LPM.dev Registry package starts private. Its owner can later opt it into Pool or Marketplace distribution from the package dashboard.

Hosted Workflows

LPM CLI is the command-line entry point for these LPM.dev Registry workflows:

  • Accounts and packages — sign in, publish packages, install licensed versions, and inspect package metadata.
  • Pool and Marketplace — install packages covered by a subscription or commercial license, and view Pool revenue as an author.
  • Environments — keep secrets encrypted locally and optionally sync them through LPM.dev Registry.
  • Tunnels — expose a local service through the hosted tunnel relay and inspect incoming requests.
  • Swift packages — configure Swift Package Manager for packages published through the Registry.

See Registry Workflows for the commands that connect these services.

LPM.dev Docs and CLI Docs

These docs explain LPM.dev Registry accounts, publishing, distribution, billing, organizations, environments, and tunnels.

The complete LPM CLI documentation lives at cli.lpm.dev. Use it for:

  • npm and private-registry compatibility
  • installation and dependency resolution
  • lockfiles, workspaces, and node_modules layouts
  • lifecycle scripts and the package store
  • the development server, runners, and local tools
  • every command, flag, configuration file, and environment variable

Start with the LPM CLI registry guide to see how one project can use npm, LPM.dev Registry, and private registries together.