This repository has been archived by the owner on May 1, 2024. It is now read-only.
Replies: 1 comment 2 replies
-
Isn't this up to the shell you're using? There are dozens of different shells and they each support autocompletion in different ways, so maybe you need to get your preferred shell to add support for npm? For instance this project looks to have been around for eight years now and adds the kind of autocompletion you're looking for to zsh. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For me it is absolutely mind blowing that npm still doesn't have autocompletion for package names in 2024.
By "package names" I don't mean searching for available packages online when I press TAB, but just currently installed packages.
For instance if I type
npm update rollup-plug
and I haverollup-plugin-node-resolve
androllup-plugin-typescript
installed in my project then the terminal should propose both packages for autocompletion when I press TAB (similar tonpm run ...
suggesting defined scripts), it works for scripts but not for installed package. Why do we have to type everything? So much unnecessary typing, I just don't understand why such a popular (and quite old now) tool doesn't have such basic features.Not only autocompletion would help us to code faster but could also serve as a small visual hint, for instance if I type
npm info jq
and press TAB, if I don't seejquery
being autocompleted then I would know it's not installed in my project.Does anyone know if
yarn
,pnpm
,bun
or another sibling of npm have this feature available?(ps: do not even get me started about
npm
not showing the version of a package I just installed usingnpm install <package_name>
(such a joke))Beta Was this translation helpful? Give feedback.
All reactions