Closed dmorda closed 4 years ago
Sorry to ask this but did you npm install?
No worries, fair question.
I did the git clone
and then npm install
. After that, I ran npm run test-pages
.
I think it's telling me the path to the Chromium app is not there, which upon inspection is correct.
/Users/myusername/Desktop/speedlify/node_modules/puppeteer/.local-chromium/mac-756035/chrome-mac/Chromium.app/Contents/MacOS/Chromium
There is no MacOS path under that folder.
ls /Users/myusername/Desktop/speedlify/node_modules/puppeteer/.local-chromium/mac-756035/chrome-mac/Chromium.app/Contents
The only folder under Content is "Frameworks".
Huh—I’m going to ask another dumb question here—are you on node 14.0.0?
I’m seeing 14.5 as the latest and it seems to work here (on Mac OS Catalina)
As it turns out, I dug into this yesterday and was able to get it working. I would do an npm install
and everything seemed to be installed correctly. The only output that was potentially related was this.
npm WARN axe-puppeteer@1.1.0 requires a peer of puppeteer@^1.10.0 || ^2.0.0 but none is installed. You must install peer dependencies yourself.
After I did the npm install
and ran npm test-pages
I would get this error:
Error: spawn /Users/dmorda/Desktop/speedlify/node_modules/puppeteer/.local-chromium/mac-756035/chrome-mac/Chromium.app/Contents/MacOS/Chromium ENOENT
That indicated that Chromium wasn't in the right place so I looked into it. Here's the output of the .local-chromium directory.
$ pwd && ls -la
/Users/dmorda/Desktop/speedlify/node_modules/puppeteer/.local-chromium
total 262184
drwxr-xr-x 4 dmorda staff 128 Jul 9 06:57 .
drwxr-xr-x 12 dmorda staff 384 Jul 9 06:54 ..
-rw-r--r-- 1 dmorda staff 130132645 Jul 9 06:57 chrome-mac.zip
drwxr-xr-x 3 dmorda staff 96 Jul 9 06:57 mac-756035
What seemed to be happening is that puppeteer would be installed during the npm install
process, but the zip file was not being extracted correctly. The Chromium.app seemed to be corrupt in some way. So I unzipped chrome-mac.zip
and then replaced the corrupt Chromium.app.
Once I did the above, all worked as expected. Since nobody else reported this, it's probably my local environment so I'm going to go ahead and close this one.
Thank you for the update!
I'm running Node 14.0.0. I cloned the repo, ran
npm install
and then when I runnpm run testpages
I get the following error:Known issue or am I doing something wrong?