query node_modules
🔍 A simple cli utility for querying the node_modules directory
most bugs are caused by the assumptions we didn't realize we were making.
When debugging a problem, I sometimes find myself checking what are the installed versions of the modules within node_modules directory. While current commands like npm list provide too much clutter and are usually not fast enough. qnm aims to get this information fast and show you only important information, while supporting both yarn & npm.
- 💬 Tab completions
- ✨ Interactive fuzzy-search
- 🔤 Match all packages with a specific string
⁉️ Why a package was installed?
npm i --global qnmqnm will also install tab completions during post install.
qnm [module]For example, if you want to see the installed versions of lodash:
qnm lodashAnd you'll see something like that:
lodash
├── 4.17.5
├─┬ cli-table2
│ └── 3.10.1
└─┬ karma
└── 3.10.1Which means you have 3 occurrences of lodash in your node_modules:
./node_module/lodash./node_module/cli-table2/node_modules/lodash./node_module/karma/node_modules/lodash
Use qnm command without arguments to trigger an fzf like fuzzy search, start typing to filter the matches from your node_modules.
Works like grep, and match's any module that includes the supplied string.
For example, i want to see which eslint plugins i have installed:
> qnm -m eslint-plug
eslint-plugin-babel
└── 3.3.0
eslint-plugin-lodash
└── 2.6.1
eslint-plugin-mocha
└── 4.12.1
eslint-plugin-react
└── 6.10.3currently only works if you installed with npm
Add information regarding why this package was installed in the first place, by showing its dependent packages.
alias: ls
Returns a list of all modules in node_modules directory.
qnm listOpen issues for bugs or feature requests and feel free to open pull requests!
For local development, fork the repo, clone, install dependencies and run the tests:
git clone [email protected]:<username>/qnm.git
cd qnm
npm install
npm test
The MIT License