npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

phantomjs2-server

v1.2.1

Published

PhantomJS 2 Selenium Server

Downloads

1

Readme

PhantomJS Server

Use PhantomJS as a drop-in replacement for your Selenium Standalone server.

This is just a simple script to start a PhantomJS webdriver instead of the Selenium standalone server.

The server.address() works the same way as the selenium-webdriver's version, by responding with a promise that will eventually resolve to the localhost address of PhantomJS.

PhantomJS is version 2.

Start a PhantomJS server with package.json pretest

To start a PhantomJS server before running your test scripts, you can create a file that is called pretest like this:

package.json

{
  ...
  "devDependencies": {
	...
    "selenium-webdriver": "2.x",
    "phantomjs-server": "2.x"
  },
  "scripts": {
	...
    "pretest": "node start-phantomjs.js",
    "posttest": "node stop-phantomjs.js",
  }
}

start-phantomjs.js

var phantomjs = require('phantomjs-server');
phantomjs.start().then(function() {
  process.exit(0);
});

stop-phantomjs.js

require('child_process').exec(process.platform === 'win32' ? 'taskkill /F /IM phantomjs.exe /T' : 'killall phantomjs',
    function (error, stdout, stderr) {
        console.log(stdout);
    });

Using phantomjs-server inline instead of selenium-server-standalone

Assuming a Selenium testing script looking something like this:

var webdriver = require('selenium-webdriver');

var SeleniumServer = require('selenium-webdriver/remote').SeleniumServer;
var server = new SeleniumServer('bin/selenium-server-standalone.jar', { port: 4444 });
server.start();

var driver = new webdriver.Builder().
  usingServer(server.address()).
  withCapabilities({ "browserName": "firefox" }).
  build();

You only need to replace this:

var SeleniumServer = require('selenium-webdriver/remote').SeleniumServer;
var server = new SeleniumServer('bin/selenium-server-standalone.jar', { port: 4444 });
server.start();

With this:

var phantom = require('phantomjs-server');
phantom.start();

So the final script looks like:

var webdriver = require('selenium-webdriver');

var phantom = require('phantomjs-server');
phantom.start();

var driver = new webdriver.Builder().
  usingServer(phantom.address()). // This part is important!
  withCapabilities({ "browserName": "phantomjs" }).
  build();

Troubleshooting

If the PhantomJS server won't start, it is probably because you have these 2 files:

  • /usr/local/lib/libssl.0.9.8.dylib
  • /usr/local/lib/libssl.dylib

Move them to something like:

  • /usr/local/lib/_libssl.0.9.8.dylib
  • /usr/local/lib/_libssl.dylib

And you should be good to go!