chore: disallow auto update of chrome browser

[vigneshshanmugam]

• This is a follow up of Run Playwright post-install script to fix chrome binary sometimes unavailable #142 and allows us to control the update of playwright effectively browsers to tie it with the proper version. Having ^ or ~ would allow minor/patch versions to be installed on user's machine/test environments if lockfiles are not taken in to account.

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #150 opened

• Start Time: 2020-11-26T11:01:21.813+0000

• Duration: 16 min 14 sec

Test stats 🧪

Test	Results
Failed	0
Passed	45
Skipped	0
Total	45

[hmdhk]

Thanks @vigneshshanmugam, Can we at least allow the patch versions? Is there a precedent for patch versions making an issue?

[vigneshshanmugam]

yeah patch versions also updates the browser https://github.com/microsoft/playwright/releases which would be an issue for us as it would trigger removing the old browser version in favor of new one. So, we need to stick with exact match.

[hmdhk]

Sounds good! I think we should separate the update cycle of the browser from the update of playwright (we can do that as part of the packaging ticket).

[hmdhk]

Just specifying the exact version would pin the version. I wasn't sure about the = syntax since it's not mentioned in the npm docs.

Suggested change

	"playwright-chromium": "=1.6.2",
	"playwright-chromium": "1.6.2",

[vigneshshanmugam]

Its part of semver https://github.com/npm/node-semver