inconsistent npm versions in package.json

[scampi]

In package.json the npm version is 2.15.1 in engines section, but it is 2.11.0 in the devDependencies section. Is this normal ?

[epixa]

Perhaps a better question is why are we even putting npm in our devDependencies? @rashidkpc git blame goes to you - is there a reason we're handling npm in this way?

[scampi]

any update on this ? ;o)

[epixa]

No update on this. I'll probably just remove it from devDependencies altogether, since it doesn't serve any purpose that I'm aware of.

[scampi]

it seems to be needed for the licenses task https://github.com/elastic/kibana/blob/master/tasks/licenses.js#L2

[epixa]

That'd do it.

[epixa]

Is this causing you an issue? It'd be good if those versions were in sync, so I'm totally down with it getting updated, but I also don't think it's outright necessary either.

[scampi]

No it is not causing an issue. I was curious why it is like that.

[epixa]

Cool! It seems to just be a mistake.

[cjcenizal]

Resolved in #7526