barretts / node-iedriver Goto Github PK

On this line the response is being referenced which is not defined anywhere in the file.

The current version of the iedriver executable is 3.13 but this package installs 3.9 Could you update the version numbers, please?

exports.binaryversion = '3.13.0';
exports.version = '3.13';

Thanks!

SeleniumHQ/selenium-google-code-issue-archive#5116

IE has this issue on 64-bit machines that can be solved by using a 32-bit driver, it would be nice to export the path for both drivers since they are downloaded anyway :)

while i using the [email protected] with the javascript code like this

require("iedriver");
var webdriver=require('selenium-webdriver');
var driver =new webdriver.Builder().forBrowser("ie").build();
driver.get("http://www.baidu.com");

and i get an Error:

Error: IEDriverServer.exe could not be found on the current PATH. Please download the latest version of IEDriverServer.exe from http://sel
enium-release.storage.googleapis.com/index.html and ensure it can be found on your system PATH.

while i use the [email protected] is ok. i think 3.5.1 has a bug.

snyk test [email protected]

Testing [email protected]...
✗ Medium severity vulnerability found on [email protected]

• desc: Regular Expression Denial of Service (DoS)
• info: https://snyk.io/vuln/npm:semver:20150403
• from: [email protected] > [email protected] > [email protected]
  Upgrade direct dependency [email protected] to [email protected] (triggers upgrades to [email protected])

I am getting 3 vulnerabilities[1 high, 2 moderate] in my project when using [email protected]

Requesting update of [email protected] to [email protected]
and as per
https://www.npmjs.com/package/npmconf
npmconf is deprecated, thus generating high vulnerability. Can this be removed?

Your wrapper has been working great for us, but we are getting slammed with problems that require us to update to use the 64 bit driver. I thought about forking your projects and creating ie64driver, but I wanted to run it by you first. Or perhaps you have a cleaner solution?

Hi, is it possible to use this for headless Selenium tests?