search

delfrrr / npm-consider

Check package dependencies before installing it
Other
463 stars 15 forks source link

Check fails with FontAwesome #19

Open MarMun opened 4 years ago

MarMun commented 4 years ago

command I run: npm-consider install

Packages I use: "@fortawesome/fontawesome-svg-core": "^1.2.25", "@fortawesome/pro-light-svg-icons": "^5.11.2", "@fortawesome/vue-fontawesome": "^0.1.8",

Error I get: Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2ffontawesome-svg-core at checkResponse (/usr/local/lib/node_modules/npm-consider/lib/getPackageDetails.js:26:9) at process._tickCallback (internal/process/next_tick.js:68:7)

F3WS commented 3 years ago

Same, still an issue...

Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2fpro-light-svg-icons at checkResponse (/usr/local/lib/node_modules/npm-consider/lib/getPackageDetails.js:26:9) at processTicksAndRejections (internal/process/task_queues.js:93:5)

Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2ffontawesome-svg-core at checkResponse (/usr/local/lib/node_modules/npm-consider/lib/getPackageDetails.js:26:9) at processTicksAndRejections (internal/process/task_queues.js:93:5)

Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2fpro-solid-svg-icons at checkResponse (/usr/local/lib/node_modules/npm-consider/lib/getPackageDetails.js:26:9) at processTicksAndRejections (internal/process/task_queues.js:93:5)

Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2freact-fontawesome at checkResponse (/usr/local/lib/node_modules/npm-consider/lib/getPackageDetails.js:26:9) at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:93:5)

brettz9 commented 3 years ago

I'm not the maintainer, but it seems, as you can see in visiting the URLs in question, that you are using a registry which requires authentication. If you use the default of https://registry.npmjs.org for the registry, you might not have the problem.

MarMun commented 3 years ago

using a registry which requires authentication.

Thats actually the case. I suggest to ignore registry in such a case (and warn about this in report)

MarMun commented 3 years ago

Sorry. Closed in error