[monorepo]: updating package version is HARD

[aslushnikov]

TL;DR: introduce a single command to update package version.

Context

After the migration to a monorepo, it's hard to update package version.

As of today, what needs to be done:

1. Update version in //package.json
2. Run npm run lint-packages. This will propagate version to sub-packages
3. Update version from old to new one in //package-lock.json and //packages/create-playwright/package-lock.json. I usually use sed for this, for BSD sed it looks like this:

   $ sed -i '' -e 's/1.16.0-next/1.16.0/g' package-lock.json
   $ sed -i '' -e 's/1.16.0-next/1.16.0/g' packages/create-playwright/package-lock.json

The last part is especially tricky. Without doing so, the npm install call just fails.

[mxschmitt]

For step 3. executing npm install should propagate it across the package-lock.json. The package-lock.json inside create-playwright gets removed soon.

Seems like after:

• chore: move create-playwright build to build.js infra #9687
• devops: release create-playwright over publish infra #9683

this seems at least partly better. and we can create a small wrapper script around this "version bumping" process for releases (update version in package.json, lint-packages, npm install)

[aslushnikov]

Unfortunately, npm i doesn't work - it crashes with some error :(

[mxschmitt]

Created npm/cli#3940 in the NPM CLI with a small repro.

[mxschmitt]

Closing for now since we have a workaround