[BUG] "No executable path is specified. Pass "executablePath" option directly" after update to Big Sur 11.1
See original GitHub issueContext:
- Playwright Version: ^1.8.0-next.1608000060809 and latest stable
- Operating System: Big Sur 11.1
- Node.js version: v14.15.1
- Browser: Chromium
- Extra: [any specific details about your environment]
System:
OS: macOS 11.1
Memory: 444.80 MB / 32.00 GB
Binaries:
Node: 14.15.1 - /usr/local/bin/node
npm: 6.14.8 - /usr/local/bin/npm
Languages:
Bash: 3.2.57 - /bin/bash
Code Snippet
const {
chromium
} = require('playwright-chromium');
(async () => {
const browser = await chromium.launch();
// ...
})();
result
(node:11975) UnhandledPromiseRejectionWarning: browserType.launch: No executable path is specified. Pass "executablePath" option directly.
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.
at Connection.sendMessageToServer (/Users/heyoo/workspace/DND/sfdx/node_modules/playwright-chromium/lib/client/connection.js:69:15)
at Proxy.<anonymous> (/Users/heyoo/workspace/DND/sfdx/node_modules/playwright-chromium/lib/client/channelOwner.js:44:61)
at /Users/heyoo/workspace/DND/sfdx/node_modules/playwright-chromium/lib/client/browserType.js:61:73
at BrowserType._wrapApiCall (/Users/heyoo/workspace/DND/sfdx/node_modules/playwright-chromium/lib/client/channelOwner.js:72:34)
at BrowserType.launch (/Users/heyoo/workspace/DND/sfdx/node_modules/playwright-chromium/lib/client/browserType.js:52:21)
at /Users/heyoo/workspace/DND/sfdx/test.js:5:34
at Object.<anonymous> (/Users/heyoo/workspace/DND/sfdx/test.js:7:3)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
Describe the bug
Dunno what to add more. Started today I think after update to latest Big Sur. Tried reinstalling node_modules, updating XCode, rebooting, etc to no avail.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Big Sur Problem?: "You do not have… - Apple Developer
Yes, I have the same situation with some of my apps too after updating to Big Sur. Tried to disable Gatekeeper in terminal:...
Read more >fix: a pretty error when browser executable is not found ... - Gitnet
If it doesn't and we were launched without custom executable path, print a helpful instruction to run `npm i ... Pass "executablePath" option...
Read more >MacOS 11 Big Sur Compatibility Info
If using an Apple M1 (non-Intel) Mac, see the Apple Silicon M1 & M2 Compatibility article. The latest UAD software is tested and...
Read more >NEW 2022! Big Sur on Unsupported Macs [2008 ... - YouTube
UPDATED FOR 2022!!! You can Install macOS Big Sur on Unsupported Macs from 2008-2013! I'll show you step-by-step how to use OpenCore Legacy ......
Read more >run puppeteer on already installed chrome on macos
You can set executablePath: '/Applications/Google Chrome.app/' ... You can browse chrome://version/ in chrome, and find executableFilePath ...
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 FreeTop 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
Top GitHub Comments
Quick fix would be adding latest to your package.json
"playwright-chromium": "^1.8.0-next.1608058261773",
until 1.7 gets released.Thanks for pointing out both. 👍 I created a corresponding patch #4724 here.