What to do and how to deal with npm WARN warnings when installing packages?

Question

npm

Hello Toaster!
Gulp completely dissipated. I set everything up for myself, everything works. But for now, it worries (or even not so, it’s correct - it’s a little annoying) that when installing all the dependencies, a npm ibunch of warnings like this fall out through:

npm WARN engine [email protected]: wanted: {"node":">=5.0.0"} (current: {"node":"4.4.5","npm":"2.15.5"})
npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to [email protected]^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: [email protected]<3.0.0 is no longer maintained. Upgrade to [email protected]^4.0.0.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to [email protected]^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

I use:
Node: v4.4.5
NPM: v2.15.5 Please
tell us how to treat this and what to do to make it disappear, not to hide it, but to fix it?
Well, so as not to get up twice: bearded, seasoned experienced people, but please tell us the difference between sudo npm installand npm install? Why is there at all sudo? What gives? Pitfalls/pros/cons/needs?

Answer 1

0. Regarding the npm WARN engine, there is a clear request to update the node engine to at least 5.0.0. Update node.
1. About deprecated - this is not your problem, this is a problem in the project's dependencies (accordingly, this is the problem of the package developer). You have 2 ways: to score, because there is nothing fundamentally terrible in this. Calculate which package has an obsolete dependency, find the package on github/npm, make a pull request with updating dependencies/kick the developer.
For details see:
stackoverflow.com/questions/35491905/npm-warn-depr...
stackoverflow.com/questions/33974189/npm-warn-depr...
stackoverflow.com/questions/34840153/npm-deprecate...
2. About sudo - gives the right to execute a command from the superuser. Read about sudo. Specifically about npm and sudo, see:
https://github.com/sindresorhus/guides/blob/master...
stackoverflow.com/questions/16151018/npm-throws-er...