Mattermost Logo
npm@6
May 22, 2018 46 words

Heads up that with PR#1239, we’re effectively switching to npm@6.

Why the change? 

Previously, doing a fresh npm install would unexpectedly change package-lock.json. Upgrading to npm@6 should resolve this going forward.

What do I need to do? 

Make sure you’re running npm@6:

npm install -g npm@6

Written by Harrison Healey - @harrison on community.mattermost.com and @hmhealey on GitHub

Join us on community.mattermost.com!