repository·master·Indexed 24 days ago
https://github.com/ranyitz/qnmA fast CLI utility for querying the node_modules directory, supporting both npm and yarn. qnm provides information on installed module versions, dependency trees, and release timing. Key features include an interactive fuzzy-search interface, a 'match' command for pattern matching, a 'doctor' command to identify heavy modules and duplications, and the ability to open package homepages or package.json files directly from the CLI.
Run qnm without any arguments to trigger an interactive, fzf-like fuzzy search interface. This allows you to browse and filter all modules in your node_modules directory.
Enter to select an item.TAB and Shift-TAB to mark multiple items.CTRL-C or ESC to exit.bunx qnmWhile qnm can be installed globally, it is recommended to use npx or bunx to run it directly for better performance.
To run without installing:
bunx qnm [module]To install globally:
npm i --global qnmbunx qnm [module]The qnm CLI has a dual-purpose fallback mode when no specific command is provided:
qnm enters a fuzzy search mode.qnm attempts to get information for that specific module.Example (Fuzzy Search):
qnmExample (Module Lookup):
qnm lodashUse the following flags to modify qnm behavior:
--no-remote: Do not fetch remote data from npm. This makes qnm run faster but provides a limited view.-o, --open: Open the module's package.json file with the default editor.-d, --debug: Show full error messages (useful for debugging).--disable-colors: Disables most colors and styling (e.g., version colors).The qnm CLI output uses a visual tree structure to represent module versions and their relationships. Here is how to interpret the symbols and columns:
node_modules/camelcase).↰ or ⇡ symbols and compared against the current version.✓ (Green): The version is equal to the latest version.⇡ (Red): The version is behind the latest version.11 months ago).├── and └─┬: Standard tree branching for nested dependencies.(package-name): Indicates sub-dependencies that caused the version requirement (e.g., (boxen, yargs-parser)).dependency of: Shows the relationship path to the module being inspected.To see the installed versions and dependency tree of a specific module, provide the module name as an argument. qnm will show the version, how long ago it was released, and the dependency paths where the module is located.
Example for lodash:
bunx qnm lodashbunx qnm lodashThe match command works like grep, returning all modules that include the supplied string.
Example to find all installed ESLint plugins:
bunx qnm match eslint-plugbunx qnm match eslint-plughomepage command opens the package's "homepage" property in your default web browser.The doctor command (experimental) identifies the heaviest modules in your node_modules directory to help understand what is consuming disk space.
To sort modules based on the amount of duplications they have:
bunx qnm doctor --sort duplicatesbunx qnm doctor --sort duplicatesThe list command (alias: ls) returns a list of all modules in the node_modules directory.
Arguments:
--deps: List the versions of direct dependencies and devDependencies.--remote: Fetch remote data (Note: this may be slow due to network requests).bunx qnm listrequiredBy and whyInfo properties help trace dependency chains. requiredBy returns an array of package names that depend on this module. whyInfo provides a simplified representation of this dependency information using simplifyRequiredByInfo.NodeModule instance to retrieve package details. Note that accessing properties like packageJson or remoteData may trigger filesystem reads or network requests via npmView if the data hasn't been loaded yet.