[BUG] Launching Chromium on Windows complains about missing libraries
See original GitHub issueContext:
- Playwright Version: 1.3.0
- Operating System: Windows 7
- Node.js version: 12.18
- Browser:Chromium
Code Snippet
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch();
const context = await browser.newContext();
const page = await context.newPage();
await browser.close();
})();
Describe the bug Chromium doesn’t work, but other browsers seems to work fine
Console Output:
G:\GitHub\quran-api>set "DEBUG=pw:api" && node dircheck.js
(node:16052) UnhandledPromiseRejectionWarning: Error: browserType.launch: Host s
ystem is missing dependencies!
Full list of missing libraries:
api-ms-win-core-winrt-error-l1-1-0.dll
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs
.
at validateDependenciesWindows (G:\GitHub\quran-api\node_modules\playwright\
lib\server\validateDependencies.js:78:11)
at async validateDependencies (G:\GitHub\quran-api\node_modules\playwright\l
ib\server\validateDependencies.js:47:16)
at async Object.validateHostRequirements (G:\GitHub\quran-api\node_modules\p
laywright\lib\server\validateDependencies.js:34:5)
at async Chromium._launchServer (G:\GitHub\quran-api\node_modules\playwright
\lib\server\browserType.js:154:13)
at async Chromium._innerLaunch (G:\GitHub\quran-api\node_modules\playwright\
lib\server\browserType.js:76:61)
at async ProgressController.run (G:\GitHub\quran-api\node_modules\playwright
\lib\progress.js:75:28)
at async Chromium.launch (G:\GitHub\quran-api\node_modules\playwright\lib\se
rver\browserType.js:62:25)
at async G:\GitHub\quran-api\dircheck.js:4:19
(node:16052) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). To termin
ate the node process on unhandled promise rejection, use the CLI flag `--unhandl
ed-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejecti
ons_mode). (rejection id: 1)
(node:16052) [DEP0018] DeprecationWarning: Unhandled promise rejections are depr
ecated. In the future, promise rejections that are not handled will terminate th
e Node.js process with a non-zero exit code.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:17 (6 by maintainers)
Top Results From Across the Web
519551 - Proguard complains about org.chromium.base ...
chromium.base.library_loader.NativeLibraries.java being missing. I think what might be happening is: Cronet does not generate NativeLibraries.
Read more >FS#75103 : [chromium] Not launching due to missing libraries ...
Description: Chromium is not launching due to missing libraries. Aditionally, Code editor (open source VScode) complains about the same missing library.
Read more >Find and fix problems using the Issues tool - Microsoft Edge ...
Opening the Issues tool · Go to a webpage that contains issues to fix. For example, open the accessibility-testing demo page in a...
Read more >Troubleshooting - Puppeteer
If you get an error that looks like this when trying to launch Chromium: ... Chromium that Puppeteer installs is missing the necessary...
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild ... shouldn't complain about missing .la files" status:RESOLVED resolution:OBSOLETE severity: ...
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
@fawazahmed0 can you please try now with
npm install playwright@next
?Just ran into this and the newest version that worked was 1.2.1. As others in the thread have said, same everything installed, same dependency walker on latest version. Here is the dependency walker for the version that works