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:
Written by Harrison Healey -
Join us on community.mattermost.com