-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get it to run on macOS #17
Comments
Sorry to ask this but did you npm install? |
No worries, fair question. I did the I think it's telling me the path to the Chromium app is not there, which upon inspection is correct.
There is no MacOS path under that folder.
The only folder under Content is "Frameworks". |
As it turns out, I dug into this yesterday and was able to get it working. I would do an
After I did the
That indicated that Chromium wasn't in the right place so I looked into it. Here's the output of the .local-chromium directory.
What seemed to be happening is that puppeteer would be installed during the 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?
The text was updated successfully, but these errors were encountered: