Headless WebKit with JS API
An NPM installer for PhantomJS, headless webkit with JS API.
Please update your package references from
npm install phantomjs
Or grab the source and
What this installer is really doing is just grabbing a particular "blessed" (by this module) version of Phantom. As new versions of Phantom are released and vetted, this module will be updated accordingly.
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 = require'path'var childProcess = require'child_process'var phantomjs = require'phantomjs'var binPath = phantomjspathvar childArgs =pathjoin__dirname 'phantomjs-script.js''some other argument (passed to phantomjs script)'childProcessexecFilebinPath childArgs// handle results
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.
By default, this package will download phantomjs from our releases. This should work fine for most people.
If github is down, or the Great Firewall is blocking github, you may need to use
a different download mirror. To set a mirror, set npm config property
https://bitbucket.org/ariya/phantomjs/downloads (the official download site)
npm install phantomjs --phantomjs_cdnurl=
Or add property into your
.npmrc file (https://www.npmjs.org/doc/files/npmrc.html)
Another option is to use PATH variable
PHANTOMJS_CDNURL=https://bitbucket.org/ariya/phantomjs/downloads npm install phantomjs
If you plan to install phantomjs many times on a single machine, you can
phantomjs binary on PATH. The installer will automatically detect
and use that for non-global installs.
PhantomJS needs to be compiled separately for each platform. This installer finds a prebuilt binary for your operating system, and downloads it.
If you check your dependencies into git, and work on a cross-platform team, then you need to tell NPM to rebuild any platform-specific dependencies. Run
as part of your build process. This problem is not specific to PhantomJS, and this solution will work for any NodeJS package with native or platform-specific code.
If you know in advance that you want to install PhantomJS for a specific architecture,
you can set the environment variables:
(to set target platform) and
PHANTOMJS_ARCH (to set target
arch are valid values for
process.platform and process.arch.
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
An extra note on Linux usage, from the PhantomJS download page:
There is no requirement to install Qt, WebKit, or any other libraries. It however still relies on Fontconfig (the package fontconfig or libfontconfig, depending on the distribution).
This is NPM's way of telling you that it was not able to start a process. It usually means:
nodeis not on your PATH, or otherwise not correctly installed.
taris not on your PATH. This package expects
taron your PATH on Linux-based platforms.
Check your specific error message for more information.
This error means that NPM was not able to install phantomjs to the file system. There are three major reasons why this could happen:
npm cache cleanto fix them.
This error means that something went wrong 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 github, preventing the installer from downloading the binary.
Try visiting 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.
Some Linux distros tried to rename
nodejs due to a package
conflict. This is a non-portable change, and we do not try to support this. The
recommends that you run
apt-get install nodejs-legacy to symlink
on those platforms, or many NodeJS programs won't work properly.
Questions, comments, bug reports, and pull requests are all welcome. Submit them at the project on GitHub. If you haven't contributed to an Medium project before please head over to the Open Source Project and fill out an OCLA (it should be pretty painless).
Bug reports that include steps-to-reproduce (including code) are the best. Even better, make them in the form of pull requests.
Copyright 2012 A Medium Corporation.
Licensed under the Apache License, Version 2.0.
See the top-level file