Bug: Bug - Error: 401 Unauthorized while installing fontawesome-common-types on macOS M2 with Yarn

[captain-aman-11]

Bug description

When attempting to install dependencies using Yarn on a macOS M2 device running macOS Sequoia 15.2, the installation fails with a 401 Unauthorized error while fetching fontawesome-common-types. The same configuration works on other machines, so this appears to be an environment-specific issue rather than a problem with authentication or Font Awesome Pro configuration.

Error Output

error Error: https://npm.fontawesome.com/@fortawesome/fontawesome-common-types/-/0.3.0/fontawesome-common-types-0.3.0.tgz: Request failed "401 Unauthorized"

What has been tried:
1. Verified .npmrc configuration, including the @FortAwesome registry and auth token.
2. Cleared Yarn and npm caches.
3. Reinstalled Node.js and npm.
4. Tested on a different network to rule out proxy/firewall issues.
5. Verified the same configuration works seamlessly on other machines.
6. Ran the installation in verbose/debug mode, confirming the request reaches the Font Awesome registry but fails with a 401 Unauthorized.

Steps to Reproduce:
1. Clone the repository containing the Font Awesome dependencies.
2. Run yarn install.
3. Observe the 401 Unauthorized error.

Expected Behavior:

Dependencies should install without errors.

PS: If I do yarn install on other laptops, it's working without errors. I've a new Mac M2. Am I missing some configuration ??

Font Awesome version

"@fortawesome/fontawesome-svg-core": "^6.1.1", "@fortawesome/free-brands-svg-icons": "^6.1.1", "@fortawesome/free-regular-svg-icons": "^6.5.1", "@fortawesome/free-solid-svg-icons": "^6.1.1", "@fortawesome/pro-duotone-svg-icons": "^6.1.1", "@fortawesome/pro-light-svg-icons": "^6.1.1", "@fortawesome/pro-regular-svg-icons": "^6.1.1", "@fortawesome/pro-solid-svg-icons": "^6.1.1", "@fortawesome/react-fontawesome": "^0.1.18",

Application and Operating System

Application and Operating System
• Terminal: ZSH
• Operating System: macOS Sequoia 15.2 (Mac M2)

Web bug report checklist

• I have included a test case because my odds go way up that the team can fix this when I do
• I have searched for existing issues and to the best of my knowledge this is not a duplicate

[tagliala]

Hello,

It looks like you're trying to download the package from the private npm repository, which is restricted to Pro users.

If you do not have a Pro subscription, please remove the relevant entries in yarn.lock and try to install Font Awesome again: it should switch to the public yarn repo

If you have a Pro subscription, the issue could be related to your configuration or license.

To troubleshoot configuration issues, please refer to the Font Awesome troubleshooting guide.

If you suspect a license issue, please contact Font Awesome support at [email protected], as we cannot address Pro subscription issues in this repository.

[captain-aman-11]

I am a Font Awesome Pro member working on an older codebase. Obtaining the actual login details for the account is not feasible at the moment. However, we are using the same token with identical configurations across other developers on the team without any issues. Is there an alternative way to authenticate using just the token?

[tagliala]

Sorry, I provided you the wrong link.

Please debug your configuration with: https://docs.fontawesome.com/web/setup/packages#5-troubleshooting-your-configuration

Please double check that the correct token is being used by yarn