lpm search

lpm search <query> [--limit <N>]

Searches the registry that matches your query:

• @lpm.dev/... queries search the lpm.dev catalogue.
• @scope/... queries follow the current project's .npmrc @scope:registry=... mapping when one exists.
• Everything else searches the current project's default .npmrc registry, or npmjs.org when no override is present.

lpm search still returns a single normalized JSON envelope, but the backing search API depends on where the query routes.

Human output is compact: each result prints the package name, an indented description when one exists, and a metadata line such as latest 1.2.3 · quality 91 · ecosystem js. Use --json when you need the full routed search envelope, including fields such as downloadCount and distribution mode.

Examples

lpm search react                    # npmjs.org (or project .npmrc default registry)
lpm search @my-co/internal          # project .npmrc scoped registry
lpm search @lpm.dev/highlight       # force lpm.dev catalogue search
lpm search "react hooks" --json     # structured output

Flags

Plus the global flags — --json is useful for piping into other tools.

See also

• lpm info — full metadata for a single package through the same routing rules
• lpm quality — quality report