npm 5 not supported

Expected Behavior

Would be awesome if lerna worked with npm 5.

Current Behavior

It kind of works today. The problem is that each time I run bootstrap something is modifying the package-lock.json files in inconsistent ways. Sometimes it removes the root level name and version from the package lock file. Sometimes it breaks and leaves the package.json in a state where it only has a list of the dependencies and a package.json.lerna_backup file exists.

Possible Solution

Something is clearly going on where potentially npm is watching modifications to the package.json and messing stuff up as lerna is modifying them. Not totally sure.

Steps to Reproduce (for bugs)

Honestly, each time I ran bootstrap I would get a different result.

lerna.json

{
  "lerna": "2.0.0",
  "packages": [
    "packages/*"
  ],
  "version": "independent"
}

Context

Executable	Version
lerna --version	2.0.0
npm --version	5.3.0
yarn --version	0.25.7
node --version	8.1.4

OS	Version
macOS Sierra	10.1.2

[bryzaguy]

Thanks for the suggestions on making the package-lock files less of an issue. However, I want to have and use the package-lock files.

[nealoke]

When I install a new package with npm 5 it removes my symblinks created by lerna bootstrap, super annoying