bridge between node.js and PhantomJS using only XHR
It is very much similar to the other bridge available, PhantomJS-Node, but is different in a few ways:
You will need to install PhantomJS first. The bridge assumes that the "phantomjs" binary is available in the PATH.
The only other dependency for using it is socket.io.
For running the tests you will need Mocha. The tests require PhantomJS 1.6 or newer to pass.
npm install node-phantom
You can use it pretty much like you would use PhantomJS-Node, for example this is an adaptation of a web scraping example :
var phantom=require'node-phantom';phantomcreatereturn phcreatePagereturn pageopen""console.log"opened site? " status;pageincludeJs''//jQuery Loaded.//Wait for a bit for AJAX content to load on the page. Here, we are waiting 5 seconds.setTimeoutreturn pageevaluate//Get what you want from the page using jQuery. A good way is to populate an object with all the jQuery commands that you need and then return the object.var h2Arr =pArr = ;$'h2'eachh2Arrpush$thishtml;;$'p'eachpArrpush$thishtml;;returnh2: h2Arrp: pArr;console.logresult;phexit;;5000;;;;;
options is an optional object with options for how to start PhantomJS.
options.parameters is an array of parameters that will be passed to PhantomJS on the commandline.
will start phantom as:
You may also pass in a custom path if you need to select a specific instance of PhantomJS or it is not present in PATH environment. This can for example be used together with the PhantomJS package like so:
Once you have the phantom instance you can use it much as you would the real PhantomJS, node-phantom tries to mimic the api.
An exception is that since this is a wrapper that does network communication to control PhantomJS, all methods are asynchronous and with a callback even when the PhantomJS version is synchronous.
Another notable exception is the page.evaluate method (and page.evaluateAsync method) that since PhantomJS 1.6 has a provision for extra arguments to be passed into the evaluated function. In the node-phantom world these arguments are placed after the callback. So the order is evaluatee, callback, optional arguments. In code it looks like :
You can also have a look at the test folder to see some examples of using the API.
Made by Alex Scheel Meyer. Released to the public domain.