Fix incorrectly migrated package-lock.json

[Minnozz]

node_modules/.bin was missing after a clean npm install

See npm/cli#2147

[ryyppy]

we need to revisit this later, since we currently have a really weird, but working setup on our team's machines that we don't want to touch rn

[Minnozz]

Could you explain the weird setup?

I think the current package-lock.json is just buggy after being recently upgraded from lockfile v1 to v2 (b1ecde6), causing the rescript and other binaries to be unavailable in npm run scripts unless you had already run an npm install in your checkout before that commit.

[ryyppy]

Right now you are supposed to use node@12 and npm@6 (this was not a typo).

npm@6 uses lockfile v1, which works perfectly fine on all our machines.
We experienced problems with lockfile version 2 though, which ended up so badly that Cheng was literally zipping up node_modules to be able to reproduce his rescript-lang.org setup.

Same for Maxim and Bettina's machine (and partly also mine).

Will have another look at it soon, right now it's too cumbersome to me to communicate yet another tooling version change for everyone.

[Minnozz]

Right, I understand. Feel free to ignore this / leave this until later, but just to clear up any confusion:

I did not migrate the lockfile to v2 in this PR, that was done a month ago in this commit: b1ecde6. I just updated the README to reflect the lockfile version that is currently in use. If you want to stay on npm@6 it would be better to revert the lockfile in the repo to v1; I could do that if you want?

The team's problems with the v2 lockfile may be the same I encountered (missing binaries)? Both downgrading to v1 or re-upgrading to v2 (this PR) would fix that.

See npm/cli#2147 for explanation of the lockfile bug.

[ryyppy]

Okay now I understand the problem. Will merge this and rebase the currently active branches.