eslint server takes ~3-5 minutes until available

I don’t know since when this is a problem but the start of the eslint server takes between 3-5 minutes here.

[Info  - 10:12:55] ESLint server is running.
[Info  - 10:16:05] ESLint library loaded from: d:\Workspaces\xxx\xxx-client\node_modules\eslint\lib\api.js

I just upgraded from eslint 3.x to 4.19.1, which didn’t help.

Any information I can provide to hunt that down?

[schmic]

As I said, what’s happing on @drw112 end is an update-check, which gets blocked by the firewall as it not goes through the proxy …

@drw112 we should try the NO_UPDATE_NOTIFIER=1 environment setting to disable that check.

[drewtownchi]

It seems to be taking a very long time on line 310 _globalNpmPath = Files.resolveGlobalNodePath(trace);

in the globalNpmPath function

It does eventually return the right path for the _globalNpmPath variable.

Looking in files.js it seems to be taking forever on the spawnSync command

Eventually stdout comes back with the npm folder in my roaming profile (Windows)

I see these log lines in the Debug Console

[dbaeumer.vscode-eslint] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for 'eslint._legacyModuleResolve', provide the URI of a resource or 'null' for any resource. extensionHostProcess.js:494 [dbaeumer.vscode-eslint] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for 'eslint.nodePath', provide the URI of a resource or 'null' for any resource. extensionHostProcess.js:494