Plugin: Update package-lock.json

[aduth]

Previously: https://github.com/WordPress/gutenberg/pull/14664/files#r271885310

This pull request seeks to update package-lock.json file per dependency changes in #14664.

Separately, we should explore why the check-local-changes npm script is not correctly identifying local changes in Travis.

[aduth]

Separately, we should explore why the check-local-changes npm script is not correctly identifying local changes in Travis.

Ah, this is probably why:

gutenberg/.travis.yml

Line 35 in b3961d0

- npm ci

npm ci doesn't update package-lock.json

Edit: Hmm, but it is supposed to exit with error status code if package-lock.json is inaccurate (reference).

[ellatrix]

Thanks! Sorry about that. Would be good to make Travis return an error. :)

[aduth]

Yeah, I'm not really sure what's going on there, even after digging further into how Travis handles errors. Based on how some other projects explicitly incorporate npm ci for the very purpose of validating package-lock.json (google/clasp#118), it seems like it should be fine as-is. I'm wondering if it has something to do with Lerna and our dependencies being defined as local file paths.

[ellatrix]

Hm, but that still wouldn't explain memize? Or do you mean something else?

[aduth]

Hm, but that still wouldn't explain memize? Or do you mean something else?

It could, since memize is a transitive dependency (it was a dependency of @wordpress/annotations; annotations is a file-path dependency in the root package.json).

gutenberg/package.json

Line 18 in 5cf4e14

"@wordpress/annotations": "file:packages/annotations",