-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check fails with FontAwesome #19
Comments
Same, still an issue... Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2fpro-light-svg-icons Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2ffontawesome-svg-core Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2fpro-solid-svg-icons Error: Response is not ok 401 Unauthorized https://npm.fontawesome.com/@fortawesome%2freact-fontawesome |
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. |
Thats actually the case. I suggest to ignore registry in such a case (and warn about this in report) |
Sorry. Closed in error |
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)
The text was updated successfully, but these errors were encountered: