An NPM wrapper for PhantomJS version 2, headless webkit with JS API.
NOTE: phantomjs v2.x is currently under heavy development. Releases should be considered unstable.
This is a fork from zeevl/phantomjs2 which beautifully installs phantomjs2 v2.0.0 on OSX.
npm install phantomjs2.0
Or grab the source and
***Note to Ubuntu users:
You will need to install the following packages:
Ubuntu 14.04:sudo apt-get install libicu52 libjpeg8 libfontconfig libwebp5Ubuntu 15.04:sudo apt-get install libicu52 libjpeg8 libfontconfig1 libwebp5 libssl1.0.0
The package has been set up to fetch and run PhantomJS using the pre-built binaries.
bin/phantomjs [phantom arguments]
And npm will install a link to the binary in
it is wont to do.
The package exports a
path string that contains the path to the
Below is an example of using this package via node.
var path =var childProcess =var phantomjs =var binPath = phantomjspathvar childArgs =path'some other argument (passed to phantomjs script)'childProcess
The major and minor number tracks the version of PhantomJS that will be installed. The patch number is incremented when there is either an installer update or a patch build of the phantom binary.
PhantomJS is not a library for NodeJS. It's a separate environment and code written for node is unlikely to be compatible. In particular PhantomJS does not expose a Common JS package loader.
This is an NPM wrapper and can be used to conveniently make Phantom available It is not a Node JS wrapper.
I have had reasonable experiences writing standalone Phantom scripts which I then drive from within a node program by spawning phantom in a child process.
Read the PhantomJS FAQ for more details: http://phantomjs.org/faq.html
This error means that something went wront with your internet connection, and the installer was not able to download the PhantomJS binary for your platform. Please try again.
Do you live in China, or a country with an authoritarian government? We've seen problems where the GFW or local ISP blocks bitbucket, preventing the installer from downloading the binary.
Try visiting the the download page manually.
If that page is blocked, you can try using a different CDN with the
env variable described above.
You can tell NPM and the PhantomJS installer to skip validation of ssl keys with NPM's strict-ssl setting:
npm set strict-ssl false
WARNING: Turning off
strict-ssl leaves you vulnerable to attackers reading
your encrypted traffic, so run this at your own risk!
If you install PhantomJS manually, and put it on PATH, the installer will try to use the manually-installed binaries.
Questions, comments, bug reports, and pull requests are all welcome. Submit them at the project on GitHub.
Bug reports that include steps-to-reproduce (including code) are the best. Even better, make them in the form of pull requests.
Originally ported to phantomjs2 by zeevl
Copyright 2012 The Obvious Corporation.
Licensed under the Apache License, Version 2.0.
See the top-level file