Skip to content
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

Update to phantomjs 2.0 #100

Open
LorenzGardner opened this issue Mar 4, 2015 · 8 comments
Open

Update to phantomjs 2.0 #100

LorenzGardner opened this issue Mar 4, 2015 · 8 comments

Comments

@LorenzGardner
Copy link
Contributor

Please consider pulling in the latest stable phantomjs.

Workaround: One could use the path option to specify a diff phantomJs than the one pulled down by npm.

@brenden
Copy link
Owner

brenden commented Mar 13, 2015

The latest version of the phantomjs package (1.9.16) does currently get pulled in, but it looks like that package hasn't yet been updated to install phantom 2.

Related issue: Medium/phantomjs#288

@davidhlee
Copy link

@lukepolo
Copy link

👍

@lukepolo
Copy link

On ubuntu Ubuntu 14.10 i was able to use : https://github.com/Pyppe/phantomjs2.0-ubuntu14.04x64
No problems so far!

@brenden
Copy link
Owner

brenden commented Apr 1, 2015

It looks like phantomjs v2 still has some issues. I'd rather just defer to the judgement of Medium/phantomjs's maintainers and wait until they move to a v2 release.

In the meantime the workaround mentioned by LorenzGardner should work fine for anyone who needs to use v2 and I'll update the readme to mention it.

@bradvogel
Copy link

For anyone following along: you can use phantomjs2 by npm installing phantomjs2 and then passing this to webshot:

phantomPath: require('phantomjs2').path

@geekbleek
Copy link

Are there any plans to move to or give the option of using slimerjs? It seems to be much more stable in terms of output reliability of screenshots than phantomjs (I'm getting renderings of all types of various "sizes" as presented by the remote end under phantomjs)

@ghost
Copy link

ghost commented Mar 7, 2016

It looks like this is now fixed with commit ecc3917

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants