Font-awesome: NPM Install problem 2

[ingrocha]

I'm trying install fortawesome pro on angular using ng add @fortawesome/angular-fontawesome and it return me this:

npm ERR! Unable to authenticate, need: Basic realm="https://npm.fontawesome.com/"

i have my .npmrc file like this:

@fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

And i try with the NPM command but it's the same response

[tagliala]

Hi!

Thanks for being part of the Font Awesome Community.

Is this the same problem as #17147 ?

Anyway, if it is something related to license, please send an email to [email protected]

[ingrocha]

So let me understand my "for life license" its turns out it wasn't for life. am i right?

And because of that i cant install in my projects fontawesome pro? and i can use the css files?

[tagliala]

So let me understand my "for life license" its turns out it wasn't for life. am i right?

Hi, the license for FA 5 is for life, but the use of the private npm repository or the pro kit cdn isn't, sorry

This is a comment by Rob to clarify: https://github.com/FortAwesome/Font-Awesome/issues/17147#issuecomment-692775989

And because of that i cant install in my projects fontawesome pro?

You can! A new page has been added to the Docs to provide instructions on how to download npm packages and use them locally (or in a self-hosted private npm repo): https://fontawesome.com/how-to-use/on-the-web/setup/using-the-npm-download

For deploy workflows, after you have downloaded npm packages, you should be able to edit package.json as explained here: https://github.com/FortAwesome/Font-Awesome/issues/17147#issuecomment-693491890

And i can use the css files?

Sure, you can do anything that does not involve npm private repository or hosted pro kits

@robmadole please review this answer, I may have missed something

[plamenh]

So let me understand my "for life license" its turns out it wasn't for life. am i right?

Hi, the license for FA 5 is for life, but the use of the private npm repository or the pro kit cdn isn't, sorry

This is a comment by Rob to clarify: #17147 (comment)

And because of that i cant install in my projects fontawesome pro?

You can! A new page has been added to the Docs to provide instructions on how to download npm packages and use them locally (or in a self-hosted private npm repo): https://fontawesome.com/how-to-use/on-the-web/setup/using-the-npm-download

For deploy workflows, after you have downloaded npm packages, you should be able to edit package.json as explained here: #17147 (comment)

And i can use the css files?

Sure, you can do anything that does not involve npm private repository or hosted pro kits

@robmadole please review this answer, I may have missed something

You can't! svg-core and common-types are behind the paywall!

[robmadole]

@plamenh the @fortawesome/fontawesome-svg-core and @fortawesome/fontawesome-common-types are both public and free:

• https://www.npmjs.com/package/@fortawesome/fontawesome-svg-core
• https://www.npmjs.com/package/@fortawesome/fontawesome-common-types

When we've seen issues it's normally because of a package-lock.json or yarn.lock. Or you still have an errant .npmrc file that it pointing to npm.fontawesome.com.

[plamenh]

@robmadole Thanks for the clarification, but I tried everything (deleting .npmrc, node_module, package-lock, etc.) and nothing worked. Plus, using the free version of the common types is unlikely to work (tried that already with packaging the files manually from the free version and it is missing the pro types/icon names).

[tafelnl]

I have a similar issue. Until recently I had no problems installing the pro package from a local file. But since a few days I get this error also.

My package.json contents looks like the following:

{
  "dependencies": {
    "@fortawesome/fontawesome-svg-core": "^1.2.17",
    "@fortawesome/free-brands-svg-icons": "^5.14.0",
    "@fortawesome/pro-light-svg-icons": "file:fontawesome/fortawesome-pro-light-svg-icons-5.14.0.tgz",
    "@fortawesome/pro-regular-svg-icons": "file:fontawesome/fortawesome-pro-regular-svg-icons-5.14.0.tgz",
    "@fortawesome/pro-solid-svg-icons": "file:fontawesome/fortawesome-pro-solid-svg-icons-5.14.0.tgz"
  },
  "devDependencies": {
    "@fortawesome/fontawesome-pro": "file:fontawesome/fortawesome-fontawesome-pro-5.14.0.tgz"
  }
}

Ergo it installs the fontawesome pro from a local directory (I have a pro license). It should not make a connection to the fontawesome server to check for license. And even if it did, it should be okay, since I am not using the npm services (excluded in my license).

$ npm i file:fontawesome/fortawesome-pro-light-svg-icons-5.14.0.tgz

npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="https://npm.fontawesome.com/"

[tafelnl]

Ah, already found the issue. I did delete the .npmrc config. But I forgot about the global variable in npm.
So running

npm config delete "@fortawesome:registry"

solved my problem