dmlemeshko / ms-edge-driver

NPM wrapper to test Chromium-based Edge browser
https://www.npmjs.com/package/ms-chromium-edge-driver
Apache License 2.0
2 stars 2 forks source link

[BUG] Proxy setting, please. #187

Open tokyo-watcher opened 3 years ago

tokyo-watcher commented 3 years ago

Describe the bug When npm install I got this error.

npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node lib/install.js npm ERR! Microsoft Edge installed. Version: 92.0.902.62 npm ERR! Downloading MS Edge Driver 92.0.902.62... npm ERR! RequestError: connect ETIMEDOUT 13.107.246.46:443: https://msedgedriver.azureedge.net/92.0.902.62/edgedriver_win64.zip npm ERR! Driver was not downloaded

For now, I comment out this line in my batch file, but I'd like to install driver.exe with npm install. set EDGEDRIVER_DOWNLOAD_ON_INSTALL=1

I found this code at geckodriver repositry. This isn't good for ms-edge-driver?

var downloadOptions = {} var proxy = process.env.HTTPS_PROXY || process.env.HTTP_PROXY || process.env.https_proxy || process.env.http_proxy || null; if (proxy !== null) { downloadOptions.agent = new proxyAgent(proxy); }

With geckodriver, I do this before install, and go well. set HTTP_PROXY=http://proxy.url:port/ set HTTPS_PROXY=http://proxy.url:port/

OS: [e.g. MacOS 10.14.6] Windows 10 (64bit)

Package version: [e.g. 0.2.4] 0.4.3

Installation: [e.g. npm/yarn] npm

To Reproduce Steps to reproduce the behavior:

  1. npm install ms-edge-driver

Expected behavior No RequestError is expected.

Additional context I'm back in my company proxy.

tokyo-watcher commented 3 years ago

I wrote this commit. https://github.com/test20161010/ms-edge-driver/commit/7d873a948d98739bdbf07e1d04718d305bce6c19

But I don't know how to confirm this version in my environment. When I specify edge-driver like this in my project package.json, "ms-chromium-edge-driver": "git+https://github.com/test20161010/ms-edge-driver.git#7d873a948d98739bdbf07e1d04718d305bce6c19",

And npm install, then, I got this error. `npm ERR! npm WARN npm ERR! npm WARN Could not resolve dependency: npm ERR! npm WARN peer jest@">=23.4 <27" from jest-mock-process@1.4.0 npm ERR! npm WARN node_modules/jest-mock-process npm ERR! npm WARN dev jest-mock-process@"^1.4.0" from the root project npm ERR! npm WARN deprecated @types/extract-zip@2.0.1: This is a stub types definition. extract-zip provides its own type definitions, so you do not need this installed. npm ERR! node:internal/modules/cjs/loader:930 npm ERR! throw err; npm ERR! ^ npm ERR! npm ERR! Error: Cannot find module 'C:\Users\test20161010\AppData\Local\npm-cache_cacache\tmp\git-clone-581047fa\lib\install.js' npm ERR! at Function.Module._resolveFilename (node:internal/modules/cjs/loader:927:15) npm ERR! at Function.Module._load (node:internal/modules/cjs/loader:772:27) npm ERR! at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:79:12) npm ERR! at node:internal/main/run_main_module:17:47 { npm ERR! code: 'MODULE_NOT_FOUND', npm ERR! requireStack: [] npm ERR! } npm ERR! npm ERR! code 1 npm ERR! npm ERR! path C:\Users\test20161010\AppData\Local\npm-cache_cacache\tmp\git-clone-581047fa npm ERR! npm ERR! command failed npm ERR! npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node lib/install.js npm ERR! npm ERR! npm ERR! A complete log of this run can be found in: npm ERR! npm ERR! C:\Users\test20161010\AppData\Local\npm-cache_logs\2021-08-06T02_13_28_012Z-debug.log

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\test20161010\AppData\Local\npm-cache_logs\2021-08-06T02_13_35_111Z-debug.log`