-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Getting "Please install @playwright/test package..." when trying to use playwright with yarn. #23314
Comments
@tvongaza you have both If you remove |
Thanks @aslushnikov , that did solve the issue, sorry I missed the breaking change note. As it looks like I wasn't the only one hitting this issue, I wonder if playwright could detect and have a more descriptive error for this case, or a depreciation warning leading up to breaking changes like this? |
Thank you for the help both, my issue is resolved with the above solution. |
I have the same issue. All i ran was
Using https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright |
Runs well locally, but there is a bug with this version that pops up when running everything in the containerized environment. Refer to: microsoft/playwright#23314
Now recommends uninstalling other packages. Fixes #23314. Example messages: ``` Please install @playwright/test package before running "npx playwright show-report" npm uninstall playwright playwright-firefox npm install -D @playwright/test ``` ``` Please install @playwright/test package before running "yarn playwright show-report" yarn remove playwright playwright-chromium playwright-firefox playwright-webkit yarn add -D @playwright/test ``` ``` Please install @playwright/test package before running "pnpm exec playwright show-report" pnpm remove playwright pnpm add -D @playwright/test ```
@Frexuz I'm having the same issue |
What fixed the issue for me
Step 1: Uninstall
|
I cannot seem to get playwright 1.34.3 working with
yarn
, even on a fresh install.I am running into issues described in #23228, but 1.34.3 did not solve them. It is exactly what @thekp describe in #23228 (comment)_
I've created a fresh install and still get this issue:
The text was updated successfully, but these errors were encountered: