Update all the package-locks

[bcmn]

Resolves #263

Fixing the out of sync package-lock.json on latest was made more difficult by the psammead-test-helpers issue -- Many of the nested packages had package-lock.json files which seemed to be pointing to 0.1.3, a version not present on NPM.

Following this issue, when pulling in latest & wanting to resolve package-lock differences, run npm run install:packages. There is an equivalent package-lock-only command: npm run ci:packages.

• I have assigned myself to this PR and the corresponding issues
• Tests added for new features
• Test engineer approval

[bcmn]

So... Working with @radiocontrolled, we observed that when the previous postinstall step was configured, npm i would fail after pulling this branch into another branch.

However, removing the postinstall script & running npm i && lerna bootstrap --ci --hoist --force-local (the content of the postinstall script) would be successful.

As such, we have removed the postinstall script & added npm i && lerna bootstrap --ci --hoist --force-local as ci:packages.

[sareh]

👍 Great investigation work!

[radiocontrolled]

re:

Following this issue, when pulling in latest & wanting to resolve package-lock differences, run npm run install:packages. There is an equivalent package-lock-only command: npm run ci:packages.

Could we document this in the readme as it will be a recurring 'gotcha'?

[pjlee11]

This looks to be working having removed the postinstall npm script and instead using npm run install:packages. Lerna bootstrap appears to hoist the nanoid dependency to the top level package.json, before then pruning nanoid out of the package.json. This results in the top level of psammead having node_modules/ containing nanoid and the site-wide-links component which had nanoid in its package.json to not require nanoid in its own node_modules/.

A screenshot of the node_modules described above

[pjlee11]

Great work 👍

[radiocontrolled]

Great job 🎆

[jamesbrumpton]

LGTM 👍