When crafting an NPM package and you want to test that you did not forget anything by simulating an installation. This is quite a handy feature. Plus, there will be, I'm sure, more third party package hosting in a near future that will be compatible with the NPM CLI.
Another advantage is that you are not forced to publish your package on the NPM package registry if you don't want to but still be able to open-source the package. Sometimes it can be quite tedious to think about checking and publishing your next versions of your packages when you could just instead merge requests and publish a git tag.
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.
When crafting an NPM package and you want to test that you did not forget anything by simulating an installation. This is quite a handy feature. Plus, there will be, I'm sure, more third party package hosting in a near future that will be compatible with the NPM CLI.
Another advantage is that you are not forced to publish your package on the NPM package registry if you don't want to but still be able to open-source the package. Sometimes it can be quite tedious to think about checking and publishing your next versions of your packages when you could just instead merge requests and publish a git tag.