I've tested ni and it is an amazing project too, but have a different approach.
ni focus only on commonly used commands and assign an alias to each one.
The SWPM key differences are:
Not limited to some commands or alias, you can use the whole Package Managers.
Flags to change his behavior on the fly, like say which Package Manager uses (for example when no lock file exists) or test the command translation.
Include a clean command to delete common folders like node_modules.
Also, have aliases (like ni) but include another set of commonly used alias like save-dev, exact-version, and others that have been requested by the users.
NVM and Volta compatible.
Detect lock files, but also work pining manually with the Package Managers (or with the use flag when even no lock file exists).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm in a project transition moving from
npmtopnpmand it is a nightmare to remember when using each one.So I decided to create a command to do this. One command will translate to the respective PM.
npmjs.com/package/swpm
Cool stuff!
I found another package which does the same. github.com/antfu/ni
I've tested
niand it is an amazing project too, but have a different approach.nifocus only on commonly used commands and assign an alias to each one.The SWPM key differences are:
node_modules.save-dev,exact-version, and others that have been requested by the users.NVMandVoltacompatible.