v1.0.0 fails with "Error: spawn UNKNOWN" on windows, previously did work with v0.2.3karma-runner/karma-phantomjs-launcher#105 Open ya, i think the tests only run on linux/osx, that's fine, it's not a real issue. 👎3 👎 ...
This still happened to me just now. Puppeteer is installed, andchrome-linux.zipis downloaded, and unzipped, but incorrectly (and not a peep about that), and then you have a broken chrome. But where's the fault? Corrupt download? Bad zip file? Broken local unzip process?
Connecting to remote server failed with the following error message Connecting to remote server failed with the following error message : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2152989776" Connecting to workgroup computers remotely Constant PowerShell st...
SourceForge in disaster recovery mode responds with temporary redirect to html document. This document contains javascript redirect to backup archive file on amazon. The html is thus saved as the contents of ZIP archive. bin-buildtries to unzip garbage, fails and says nothing about it. Runs buil...
unzip-response@1.0.2 | | | | `-- url-parse-lax@1.0.0 | | | | `-- prepend-http@1.0.4 | | | +-- registry-auth-token@3.1.0 | | | `-- registry-url@3.1.0 | | +-- lazy-req@1.1.0 | | +-- semver-diff@2.1.0 | | `-- xdg-basedir@2.0.0 | | `-- os-homedir@1.0...
In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 👍 29 pubmikeb changed the title Error: Failed to launch the browser process! spawn \node_modules\puppeteer\.local-chromium\win64-737027\chrome-win\chrome.exe ENOENT ...