Getting "Unable to find type" Error when trying to install playwright
See original GitHub issueWhile following these set up steps trying to install Playwright on my Mac: https://playwright.dev/dotnet/docs/intro#installing-playwright
I’m getting the following error when executing this command: pwsh bin/Debug/net6.0/playwright.ps1 install
Error: InvalidOperation: /Users/–/–/Test/bin/Debug/net6.0/playwright.ps1:5:6 Line | 5 | exit [Microsoft.Playwright.Program]::Main($args) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Unable to find type [Microsoft.Playwright.Program].
Has anyone been able to overcome this issue?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Unable to install playwright on a Windows due to not ...
Unable to install playwright on a Windows due to not recognizing argument. I have verified on my windows that I have Powershell -...
Read more >Installation | Playwright
Run the install command and select the following to get started: Choose between TypeScript or JavaScript (default is TypeScript); Name of your Tests...
Read more >Browsers
Each version of Playwright needs specific versions of browser binaries to operate. You will need to use the Playwright CLI to install these...
Read more >Getting started - VS Code
Get started by installing Playwright and generating a test to see it in action. Alternatively you can also get started and run your...
Read more >Playwright Library
For certain types of errors Playwright uses specific error classes. These classes are available via playwright.errors . An example of handling a timeout...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Want to report that uninstalling my current version of pwsh and installing the latest fixed this issue for me. Went from 7.0.0 to 7.3.2.
Closing since we can’t repro and it seems stale. If you find something useful why this is happening, let us know and we’re happy to adjust documentation, since this is the first time this issue is occuring for our users.