selenium-standalone - npm Package Compare versions

Comparing version 2.43.1-4 to 2.43.1-5

conf.js

		@@ -19,4 +19,5 @@ var path = require('path');
		// see http://selenium-release.storage.googleapis.com/index.html
		v: '2.43.0'
		v: '2.43.0',
		arch: process.env.IEDRIVER_ARCH !== undefined ? process.env.IEDRIVER_ARCH : process.arch
		}
		};

install.js

		@@ -179,5 +179,5 @@ var async = require('async');
		function getIeDriverPlatform() {
		if (process.arch === 'ia32') {
		if (conf.ieDr.arch === 'ia32') {
		return 'Win32';
		} else if (process.arch === 'x64') {
		} else if (conf.ieDr.arch === 'x64') {
		return 'x64';
		@@ -184,0 +184,0 @@ } else {

package.json

		{
		"name": "selenium-standalone",
		"version": "2.43.1-4",
		"version": "2.43.1-5",
		"description": "installs a `start-selenium` command line to start a standalone selenium server with chrome-driver",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -15,3 +15,3 @@ # selenium-standalone
		```shell
		npm install --production selenium-standalone@latest -g
		npm install selenium-standalone@latest -g
		start-selenium
		@@ -76,2 +76,14 @@ ```

		## IEDriverServer architecture

		IEDriverServer 32/64bit version is downloaded according to processor architecture. There are [known issues with sendkeys](https://code.google.com/p/selenium/issues/detail?id=5116) being slow on 64bit version of Internet Explorer. To address this issue, IEDriverServer architecture can be configured using IEDRIVER_ARCH environment variable. Supported values are `ia32` and `x64`.

		### Example: Force 32bit IEDriverServer to be used

		```shell
		set IEDRIVER_ARCH=ia32
		npm install selenium-standalone@latest -g
		start-selenium
		```

		`selenium-standalone` versions maps `selenium` versions.

New alerts