Should I have npm as dependency in package.json?

Question

If you accidentally execute npm i npm it adds npm as a dependency to the package.json and adds entries to the package-lock.json.

Should I revert this? Or does it actually make sense to have npm as dependency in the package.json?

Possible duplicate of https://stackoverflow.com/questions/50399097/is-it-okay-to-include-npm-in-devdependencies-in-package-json — Estus Flask, Jun 10 '18 at 18:58
Is there a way to require a minimum npm version in my dev team? I thought maybe having npm in package.json might do this. — el-lugy, Jun 10 '18 at 19:09
@el-lugy Is there a reason you need a particular version of NPM? A lot of people don't even use NPM, they use Yarn and such... — Brad, Jun 10 '18 at 19:30

score 5 · Answer 1 · answered Jun 10 '18 at 21:19

5

npm or other package managers are meant to be installed globally.

If you wish to specify the minimum npm version for your project, you could add this to package.json

"engines" : {
  "npm" : ">=x.x.x"
}

answered Jun 10 '18 at 21:19

kit

score -1 · Answer 2 · answered Jun 10 '18 at 19:27

-1

No, you don't need to have NPM as the dependency in package.json file.

answered Jun 10 '18 at 19:27

Harshal Yeole

2 Answers2