You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The Free Package
If you need just the Free icons, we have a slimmed-down free-only package for that. Install with this command:
yarn add @fortawesome/fontawesome-free"
get this output:
➜ boiler git:(main) ✗ yarn add @fortawesome/fontawesome-free
yarn add v1.22.11
[1/4] Resolving packages...
error An unexpected error occurred: "https://npm.fontawesome.com/@fortawesome%2ffontawesome-free: authentication required".
info If you think this is a bug, please open a bug report with the information provided in "/home/foo/code/boiler/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Expected behavior
I expect the package to load without asking for me to authenticate
The text was updated successfully, but these errors were encountered:
Did you ever find a solution to this? I'm facing a similar issue in 0.2.0
on my local machine all is fun and games, then I'm pushing to github and trying to run
npm ci inside a github action and it just fails saying:
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
I've tried about everything now and I'm just lost looking for any similar issues here
running lts version of node and npm, using only
Describe the bug
Following instructions on install page https://fontawesome.com/docs/web/setup/packages#the-free-package
"The Free Package
If you need just the Free icons, we have a slimmed-down free-only package for that. Install with this command:
yarn add @fortawesome/fontawesome-free
"get this output:
Expected behavior
I expect the package to load without asking for me to authenticate
The text was updated successfully, but these errors were encountered: