qnm mit Homebrew installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

• qnm

Projektgeschichte

qnm originated from the maintainer's need for a faster, more focused way to check versions installed under node_modules than npm list or manual package.json inspection.

The tool expanded into an interactive and monorepo-aware inspector with substring matching, dependency explanations, release-age information, package homepage lookup, and a doctor command for duplication and disk-use analysis.

Adoptionsgeschichte

The project supports npm and Yarn dependency layouts, including monorepos, and its README now recommends ephemeral execution with npx or bunx while retaining global npm installation as an option. source_facts.package-manager also records Homebrew packaging.

Wie es verwendet wird

Running qnm with a package name reports installed occurrences and their dependency paths. Running it without arguments opens fuzzy search; match filters package names; list inventories modules; doctor highlights duplication and heavy packages; --no-remote avoids npm registry queries.

Warum Paket-Nerds sich dafür interessieren

qnm is explicitly a package-inspection tool for people who care about dependency trees: it exposes duplicated versions, dependency paths, release age, fuzzy search, and disk-heavy modules more directly than broad package-manager listings.

Zeitleiste

• The official sources reviewed do not provide a concise dated release timeline.
• Current documentation: On-demand execution with npx or bunx is recommended over the project's former global-install-first workflow.

Related projects

• npm and Yarn create the dependency trees qnm inspects; npx and bunx are the recommended on-demand launchers; Bun is used as a fast execution route rather than as qnm's package database.

Quellen

• Official repository and README: https://github.com/ranyitz/qnm
• Package adoption: source_facts.package-manager