-
Notifications
You must be signed in to change notification settings - Fork 607
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
v3.0.25 npm install failing on phantomjs #545
Comments
Same here on Ubuntu 17.04 with node v8.9.0 and npm 5.5.1 trying to install BackstopJS v3.0.32. |
Hmmm. No idea. This is not an issue for most users so I am guessing it’s an env issue. Maybe you could try doing a verbose install of phantom-prebuilt by its self — maybe that would turn up some clues? |
Hello All, Same here. System Info: Would you please take time to see it? Thank you, `Installing BackstopJS v3.0.25...
Considering PhantomJS found at /usr/bin/phantomjs Received 22866K total. npm ERR! A complete log of this run can be found in: |
I found the followings: Hope could help others. For mine, I use the node6.x, and npm3.x to install the backstopjs v3.0.25 on centos7 (yum install nodejs). |
I fixed it by setting user/group of /usr/lib/node_modules/ (OS: Ubuntu 17.04) to my user and install BackstopJS globally without sudo:
No BackstopJS problem, but a npm/phantomJS one.. |
@tbal Thank you, it works if not installing as root! Thank you! |
Using the same example as @tbal on OSX, I had to use:
|
Try the following.
|
I followed the instructions set out by @Kenith and this did the trick. |
@garris I am encountering this issue currently. It might be due to proxy issues. However, I was thinking, should we just have a release where puppeteer is the only engine? |
Hi @marcdacz -- phantom has been removed from the next release. Would be great if some people could validate the canary...
Cheers. |
macOS 10.12.6
node -v v8.4.0
npm -v 5.4.1
Updated to latest version of backstopjs which fails at phantomjs. Relevant portion of log below.
I'll downgrade for now, but any idea what might be causing this?
The text was updated successfully, but these errors were encountered: