From e4a7860b7c6209ae148616bc31db990a2e948b83 Mon Sep 17 00:00:00 2001
From: Dirk Eismann <dirk.eismann@sennheiser.com>
Date: Tue, 4 Sep 2018 15:51:31 +0200
Subject: [PATCH] fix: read npm registry from npm config instead of hard-wiring
 it to npmjs.org, fixes #3866

---
 lib/node-package-manager.ts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lib/node-package-manager.ts b/lib/node-package-manager.ts
index b8da3ee23a..1a82ac4cae 100644
--- a/lib/node-package-manager.ts
+++ b/lib/node-package-manager.ts
@@ -120,7 +120,8 @@ export class NodePackageManager implements INodePackageManager {
 	}
 
 	public async getRegistryPackageData(packageName: string): Promise<any> {
-		const url = `https://registry.npmjs.org/${packageName}`;
+		const registry = await this.$childProcess.exec(`npm config get registry`);
+		const url = registry.trim() + packageName;
 		this.$logger.trace(`Trying to get data from npm registry for package ${packageName}, url is: ${url}`);
 		const responseData = (await this.$httpClient.httpRequest(url)).body;
 		this.$logger.trace(`Successfully received data from npm registry for package ${packageName}. Response data is: ${responseData}`);