Heads up that with PR#1239, we’re effectively switching to npm@6.
Previously, doing a fresh npm install would unexpectedly change package-lock.json. Upgrading to npm@6 should resolve this going forward.
Make sure you’re running npm@6:
npm install -g npm@6