fix: use another npm endpoint to check for package existence (#101)

coralproject · Jun 17, 2020 · a1aa2c0 · a1aa2c0
1 parent 3599c91
commit a1aa2c0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/plugins.ts b/src/plugins.ts
@@ -229,7 +229,7 @@ export default class Plugins {
   private async npmHasPackage(name: string): Promise<boolean> {
     try {
       const http: typeof HTTP = require('http-call').HTTP
-      const url = `${this.npmRegistry}/-/package/${name.replace('/', '%2f')}/dist-tags`
+      const url = `${this.npmRegistry}/${name.replace('/', '%2f')}`
       await http.get(url)
       return true
     } catch (error) {

diff --git a/test/commands/plugins/index.test.ts b/test/commands/plugins/index.test.ts
@@ -45,7 +45,7 @@ describe('command', () => {
 
   test
   .nock('https://registry.npmjs.org', api => api
-  .get('/-/package/@heroku-cli%2fplugin-stubbed/dist-tags')
+  .get('/@heroku-cli%2fplugin-stubbed')
   .reply(503, ''))
   .command(['plugins:install', 'stubbed'], {reset: true})
   .catch(/HTTP Error 503/)