Dev
Zero-config dev server, task runner, built-in dev tools, and managed runtimes.
LPM's development surface. The marquee command is lpm dev — one command that picks up managed runtimes, syncs deps, loads .env, optionally serves over HTTPS, optionally exposes a public tunnel, and orchestrates multi-service projects. The rest of this section is the supporting cast: a parallel + cached task runner, runners for test / bench / lint / fmt / type-check / bundle / pack, and the runtime + env management around it.
For a step-by-step walkthrough, see Zero-config dev server.
Run scripts + tasks
lpm dev
Zero-config dev server with HTTPS, tunnel, env loading, and multi-service orchestration.
lpm run
Run package.json scripts. Parallel, cached, watchable, workspace-aware.
lpm exec
Run a JS/TS file directly — no package.json script entry needed.
lpm dlx / lpx
Run a package binary without installing it into the project.
Test + bench
lpm test
Auto-detect and run vitest / jest / mocha. Workspace-aware with --filter / --affected.
lpm bench
Auto-detect and run vitest bench, or your scripts.bench fallback.
Lint, format, type-check, bundle, pack (built-in tools)
lpm lint
Backed by Oxlint — lazy-downloaded, version-pinned, no npx round-trip.
lpm fmt
Backed by Biome — same pinning + caching model.
lpm bundle
Backed by a managed Rolldown engine with a verified cached package layout.
lpm pack
Backed by the project's tsdown install, wrapped in LPM's workspace and JSON contract.
lpm check
TypeScript check (tsc --noEmit) against the project-local install.
lpm plugin
Manage installed built-in tool plugins (list, update, remove).
Runtime + environment
lpm use
Install and pin managed Node.js or Bun versions. Auto-installs on first use of a pinned version.
lpm env
Per-project secrets — set / get / list / push / pull / pair / OIDC. Encrypted local storage with optional cloud sync.
Features (concept pages)
Task runner
Parallel + cached execution model behind lpm run and lpm dev's services.
Test + bench auto-detection
How lpm test and lpm bench pick a runner — vitest, jest, mocha, or scripts fallback.
Built-in tools
How plugin-backed tools, project-local wrappers, and managed engines fit together.
Managed runtimes
Node and Bun detection order, auto-install, storage, and script PATH behavior.