yo: 🐛 yo version check fails while behind proxy

Type of issue

🐛 bug

---

My environment

• OS version/details: Windows 10 64-bit
• Node version: 10.5.0
• npm version: 6.1.0
• Version of yo : 2.0.3

Expected behavior

I expect the version check to use the same proxy settings as npm does.

Current behavior

At work I’m sitting behind a company proxy and for some reason the version check fails while the install succeeds.

Command line output

PS C:\Users\xxqqvc\Projects\test> npm init -y
PS C:\Users\xxqqvc\Projects\test> ls

    Directory: C:\Users\xxqqvc\Projects\test


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       2018-07-04     11:48            200 package.json


PS C:\Users\xxqqvc\Projects\test> npm i --save yo

> spawn-sync@1.0.15 postinstall C:\Users\xxqqvc\Projects\test\node_modules\spawn-sync
> node postinstall


> yo@2.0.3 postinstall C:\Users\xxqqvc\Projects\test\node_modules\yo
> yodoctor


Yeoman Doctor
Running sanity checks on your system

√ Global configuration file is valid
√ NODE_PATH matches the npm root
√ Node.js version
√ No .bowerrc file in home directory
√ No .yo-rc.json file in home directory
{ RequestError: connect ETIMEDOUT 104.18.97.96:443
    at ClientRequest.req.once.err (C:\Users\xxqqvc\Projects\test\node_modules\latest-version\node_modules\got\index.js:73:21)
    at Object.onceWrapper (events.js:273:13)
    at ClientRequest.emit (events.js:182:13)
    at TLSSocket.socketErrorListener (_http_client.js:382:9)
    at TLSSocket.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  code: 'ETIMEDOUT',
  message: 'connect ETIMEDOUT 104.18.97.96:443',
  host: 'registry.npmjs.org',
  hostname: 'registry.npmjs.org',
  method: 'GET',
  path: '/yo' }
× yo version
{ RequestError: connect ETIMEDOUT 104.18.97.96:443
    at ClientRequest.req.once.err (C:\Users\xxqqvc\Projects\test\node_modules\latest-version\node_modules\got\index.js:73:21)
    at Object.onceWrapper (events.js:273:13)
    at ClientRequest.emit (events.js:182:13)
    at TLSSocket.socketErrorListener (_http_client.js:382:9)
    at TLSSocket.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  code: 'ETIMEDOUT',
  message: 'connect ETIMEDOUT 104.18.97.96:443',
  host: 'registry.npmjs.org',
  hostname: 'registry.npmjs.org',
  method: 'GET',
  path: '/yo' }
× yo version

Your yo version is outdated.

Upgrade to the latest version by running:
npm install -g yo@latest

(node:6016) UnhandledPromiseRejectionWarning: Error: callback() can only be called once.
    at onetime (C:\Users\xxqqvc\Projects\test\node_modules\each-async\node_modules\onetime\index.js:15:11)
    at rule.verify.err (C:\Users\xxqqvc\Projects\test\node_modules\yeoman-doctor\lib\index.js:23:7)
    at binVersionCheck.then (C:\Users\xxqqvc\Projects\test\node_modules\yeoman-doctor\lib\rules\yo-version.js:21:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:6016) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:6016) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
√ npm version

Found potential issues on your machine :(
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN test@1.0.0 No description
npm WARN test@1.0.0 No repository field.

+ yo@2.0.3
added 535 packages from 262 contributors and audited 1892 packages in 281.485s
found 0 vulnerabilities