Upgrade to PhantomJS 2.1.1

Well, for starters 1.9.1 seems to currently fail to install on windows due to ws version failing currently. Which is due to socket.io having issues. 2.x doesn't have the issue

Maciej Brencz · Answer 7 · Sat Jun 06 2015 02:03:05 GMT+0800 (China Standard Time)

package.json:

+    "phantomjs": "Medium/phantomjs#version-2.0",

$ npm update phantomjs 
/
> phantomjs@2.0.0-alpha1 install /home/macbre/src/github/phantomas/node_modules/phantomjs
> node install.js

There is no prebuilt binary for your platform: linux x64 3.13.0-54-generic
You should install phantomjs from source, put the binary on your PATH, and try again

Maciej Brencz · Answer 8 · Sat Jun 06 2015 17:39:07 GMT+0800 (China Standard Time)

Forked phantomjs npm module to use the latest PhantomJS 2.0 binaries (unofficial ones) and Ubuntu 12.04 binaries for Travis CI.

Martin Spierings · Answer 9 · Wed Jun 10 2015 05:40:58 GMT+0800 (China Standard Time)

So we're getting some progress?

Eric Mill · Answer 10 · Thu Jul 02 2015 04:50:42 GMT+0800 (China Standard Time)

I believe PhantomJS 2 has better support for SNI -- the lack of support in PhantomJS 1 makes phantomas fail on HTTPS sites which require SNI.

Maciej Brencz · Answer 11 · Thu Jul 02 2015 05:23:42 GMT+0800 (China Standard Time)

@Martinspire, no progress. Still waiting for 32-bit and Debian-compatible binaries.

I think we'll end up forking phantomjs npm module and compiling "our" own PhantomJS 2.0 binaries with statically-linked libraries.

Maciej Brencz · Answer 12 · Sat Jul 04 2015 02:07:55 GMT+0800 (China Standard Time)

Good news, everyone :)

I've managed to compile PhantomJS 2 binary using Docker (running Ubuntu 14.04 image) with statically-linked libraries (#540 / macbre/phantomjs2-npm#1). It runs smoothly on Debian 8.1 amd64.

Eric Mill · Answer 13 · Sat Jul 04 2015 04:31:53 GMT+0800 (China Standard Time)

That's fantastic! I added myself as a subscriber to #531, and will happily test phantomas out on a batch of .gov sites I watch, once it's out.

Maciej Brencz · Answer 14 · Sat Jul 11 2015 19:21:46 GMT+0800 (China Standard Time)

@konklone, @gmetais - #531 is now merged into devel branch. You can use PhantomJS 2.0.0 by settings an environment variable:

PHANTOMAS_ENGINE=webkit2 phantomas "http://example.com"

or passing --engine=webkit2 option.

webkit (i.e. PhantomJS 1.9.x) will still be a default because of huge problems with Linux binaries for PhantomJS 2.0.0.

Gaël Métais · Answer 15 · Sat Jul 18 2015 21:42:47 GMT+0800 (China Standard Time)

Thanks for your great work!

It fails on OSX, here is the debug log:

DEBUG=* node bin/phantomas.js http://www.google.fr --engine=webkit2
  optimist:config parse: ["node","/Users/gaelmetais/Documents/GitHub/phantomas/bin/phantomas.js","http://www.google.fr","--engine=webkit2"] +0ms
  optimist:config options: {"_":["node","/Users/gaelmetais/Documents/GitHub/phantomas/bin/phantomas.js","http://www.google.fr"],"version":false,"V":false,"help":false,"h":false,"verbose":false,"v":false,"disable-js":false,"no-externals":false,"scroll":false,"spy-eval":false,"stop-at-onload":false,"analyze-css":false,"colors":false,"film-strip":false,"page-source":false,"progress":false,"silent":false,"engine":"webkit2","ssl-protocol":"any","timeout":15,"reporter":"plain","R":"plain","format":"plain","$0":"node ./bin/phantomas.js"} +1ms
  phantomas:cli Preparing 1 run(s)... +1ms
  phantomas nodejs v0.10.33 +1ms
  phantomas phantomas v1.11.0 installed in /Users/gaelmetais/Documents/GitHub/phantomas +0ms
  phantomas URL: <http://www.google.fr> +0ms
  phantomas Options: {"version":false,"V":false,"help":false,"h":false,"verbose":false,"v":false,"disable-js":false,"no-externals":false,"scroll":false,"spy-eval":false,"stop-at-onload":false,"analyze-css":false,"colors":false,"film-strip":false,"page-source":false,"progress":false,"silent":false,"engine":"webkit2","ssl-protocol":"any","timeout":15,"reporter":"plain","R":"plain","format":"plain"} +0ms
  phantomas Temporary directory: /var/folders/5h/_fm174694_x75lcs7y9tt9xc0000gn/T//phantomas/d5e9d76c-9769-454b-8896-64195879e96f/ +4ms
  phantomas:engines Engine "webkit": PhantomJS v1.9.8 installed in /Users/gaelmetais/Documents/GitHub/phantomas/node_modules/phantomjs/lib/phantom/bin/phantomjs +3ms
  phantomas:engines Engine "webkit2": PhantomJS v2.0.0 installed in /Users/gaelmetais/Documents/GitHub/phantomas/node_modules/phantomjs2/lib/phantom/bin/phantomjs +6ms
  phantomas:engines Engine "gecko": SlimerJS v0.9.5 installed in /Users/gaelmetais/Documents/GitHub/phantomas/node_modules/slimerjs/lib/slimer/slimerjs +5ms
  phantomas:engines Running /Users/gaelmetais/Documents/GitHub/phantomas/scripts/phantomas.js (using PhantomJS) +1ms
  phantomas:engines Passing phantomas options: {"version":false,"V":false,"help":false,"h":false,"verbose":false,"v":false,"disable-js":false,"no-externals":false,"scroll":false,"spy-eval":false,"stop-at-onload":false,"analyze-css":false,"colors":false,"film-strip":false,"page-source":false,"progress":false,"silent":false,"engine":"webkit2","timeout":15,"reporter":"plain","R":"plain","format":"plain","url":"http://www.google.fr","user-agent":"phantomas/1.11.0 (PhantomJS/2.0.0; darwin x64)"} +0ms
  phantomas:engines Passing engine options: ["--debug=false","--ssl-protocol=any"] +0ms
  phantomas Spawned with pid #52344 +4ms
phantomas: (255) Engine crashed unexpectedly
  phantomas:results Process returned code #255 +6ms
  phantomas:results Error when parsing JSON (SyntaxError: Unexpected end of input) +0ms
  phantomas:runs results [1]: [[{},null]] +1ms
  phantomas:runs Run #1 did not complete - err #255 +0ms
  phantomas:runs err: "255" +1ms
  phantomas:runs Exiting with code #255 +0ms

It's working correctly in an Ubuntu VM, I'm going to make some comparison tests between 1.9 and 2.0 :)

Gaël Métais · Answer 16 · Sat Jul 18 2015 22:53:36 GMT+0800 (China Standard Time)

This is working great on Linux.

Fixes these bugs:

SSL problems on some websites (error 254)
JS errors on ECMAScript 5 such as with 'Function.prototype.bind'

Maciej Brencz · Answer 17 · Sat Jul 18 2015 23:35:54 GMT+0800 (China Standard Time)

Great!

As for the OSX problems - can you run phantomas with --debug argument and provide the output?

Gaël Métais · Answer 18 · Sat Jul 18 2015 23:45:08 GMT+0800 (China Standard Time)

There's not more output with the --debug argument:

node bin/phantomas.js http://www.google.fr --engine=webkit2 --debug
  phantomas: (255) Engine crashed unexpectedly

Maciej Brencz · Answer 19 · Sun Jul 19 2015 17:18:26 GMT+0800 (China Standard Time)

@gmetais, it seems that PhantomJS segfaults on OSX. Can you reproduce this issue on different URLs?

Gaël Métais · Answer 20 · Sun Jul 19 2015 18:13:25 GMT+0800 (China Standard Time)

On any URL. In fact, it fails so quickly (less than 250ms, I guess) that it probably doesn't have the time to start calling the URL.

Gaël Métais · Answer 21 · Sat Sep 05 2015 03:51:03 GMT+0800 (China Standard Time)

Hey @macbre!

For your information, the public http://yellowlab.tools instance has been using PhantomJS 2 for one week, testing hundreds of websites, and no-one has complained yet! (It's using your devel branch.)

Just wanted to share this good news!

Maciej Brencz · Answer 22 · Sat Sep 05 2015 04:58:12 GMT+0800 (China Standard Time)

Glad to hear that :)

Maciej Brencz · Answer 23 · Sat Sep 05 2015 21:20:18 GMT+0800 (China Standard Time)

Since #531 PhantomJS 2.0 is one of supported engines.

Because of problems with statically linked binaries for Linux, I'm not going to make PhantomJS 2 a default engine, yet.

Maciej Brencz · Answer 24 · Wed Jan 27 2016 23:57:38 GMT+0800 (China Standard Time)

ariya/phantomjs#12970 - PhantomJS 2.1 released!

Maciej Brencz · Answer 25 · Sat Jan 30 2016 19:00:57 GMT+0800 (China Standard Time)

It did take a while, but we can now use official binaries for PhantomJS 2.x,

lion_bash · Answer 26 · Sat Jun 13 2020 05:04:38 GMT+0800 (China Standard Time)

Was there a resolution for this I'm getting the following issue (phantomjs 2.1.1, and phantomas v1.20.1):

phantomas http://google.com

/usr/lib/node_modules/phantomas/lib/engines.js:57
			throw 'Engine "' + this.options.engine + '" not found!';
			^
Engine "webkit2" not found!
(Use `node --trace-uncaught ...` to show where the exception was thrown)