fix(build): playwright cannot find browser executables in a new env #3721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For a new development environment,
pnpm build
fails due to missing browser deps for playwright tests with error messages like:It is required to install manually with
pnpm exec playwright install
withinapps/wing-console/console/app
, which breaks thepnpm build
flow.This fix is a try to ensure the browser deps are always installed and being the latest before running tests. It works fine for local development. Although the installation "runs" before every test run, turbo does a pretty good job to cut corners:
Just not sure about if this is okay for the CI environment, please suggest
Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.