Font-awesome: [PRO] Fontawesome packages are not found in the npm registry.

[pardonmeme]

Describe the bug
What happened? What are you seeing? How did you arrive here?
Until now I was always using the file .npmrc to get packages with fontawesome PR and it worked perfectly fine. But since last friday, all our build fails because the packages cannot be found in npm registry. Did something changed?

To Reproduce
Have a fontawesome pro version and try to install with the .npmrc alias and the token

Expected behavior
How would you like this to work instead?
I would expected the fontawesome pro to be found in the npm registry and be installed.

Screenshots

Version and implementation
"@fortawesome/fontawesome-svg-core": "^1.2.25",
"@fortawesome/pro-duotone-svg-icons": "^5.11.2",
"@fortawesome/pro-light-svg-icons": "^5.11.2",
"@fortawesome/pro-regular-svg-icons": "^5.11.2",
"@fortawesome/pro-solid-svg-icons": "^5.11.2",
"@fortawesome/react-fontawesome": "^0.1.5",

Bug report checklist

• [ x] I have filled out as much of the above information as I can
• [x ] I have searched for existing issues and to the best of my knowledge this is not a duplicate

[GonzaSanchez]

Hey! i was able to download it again by updating my .npmrc. I didn't know it has a different syntax
https://fontawesome.com/how-to-use/on-the-web/setup/using-package-managers

[tagliala]

Hi!

Thanks for being part of the Font Awesome Community.

Please check your .npmrc as @GonzaSanchez mentioned

Then feel free to send an email to [email protected]

[GonzaSanchez]

Also you should uninstall all your fontawesome deps, check that your lock file doesn't any fontawesome deps and then reinstall it. This is because the .npmrc removed the token from the url, but the lock file still had it in the url.

[pardonmeme]

That is quite a big of a breaking change, all previous CI builds fails now with the previous .npmrc setup.
True, after updating and removing package-lock and reinstalling again node_modules it worked but still.

[tagliala]

Hi, is this still an issue?

[Turbotailz]

In my case, my .npmrc file was using the correct format but I was still getting 404 errors. Simply removing package-lock.json and running npm i again resolved the issue for me.