search

FortAwesome / Font-Awesome

The iconic SVG, font, and CSS toolkit
https://fontawesome.com
Other
74.35k stars 12.21k forks source link

Unable to download "fontawesome-free" on my Vue.js application during application build #17737

Open Apekshagb opened 3 years ago

Apekshagb commented 3 years ago

Describe the bug Until last Thursday I was able to build and install "fontawesome-free" package for my Vue.js application but since Friday I have not been able to build my application and it keeps throwing me the following error.

To Reproduce It is an internal application within our organization, hence we are not allowed to share anything link.

Describe any details about the test case that we need to know like "whatever you do, don't click the red button." We are using the "fontawesome-free" package for the icons within our Vue files.

Expected behavior The build should be able to download the package and successfully compile the code.

Screenshots If applicable, add screenshots to help explain your problem.

Version and implementation Version: Browser and version:

Bug report checklist

tagliala commented 3 years ago

and it keeps throwing me the following error.

Hi, the error is missing

Apekshagb commented 3 years ago

Here, this is what we get:

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

tagliala commented 3 years ago

Looks like a license issue. Do you have a Font Awesome Pro account with a valid license?

anjeshgoud commented 3 years ago

@tagliala

to validate the license for Font Awesome Pro active or expiry do we have any link (using "_authToken " )

essenmitsosse commented 3 years ago

Does this happen on all builds or only on builds triggered by Dependabot? If so, you might want to look into this: https://github.com/dependabot/dependabot-core/issues/3253#issuecomment-799781478

(We had the same problem and this issue has changed the build behaviour for us from one day to the other)

tagliala commented 3 years ago

@anjeshgoud sorry, but I didn't get the answer

We have several scenarios:

  1. You have an active Font Awesome Pro subscription and you need pro packages in that application: please double check that your .npmrc configuration is correct: https://fontawesome.com/how-to-use/on-the-web/setup/using-package-managers#installing-pro
  2. You have an active Font Awesome Pro subscription, but you just need free packages like fontawesome-free in that application: please make sure that there aren't .npmrc files pointing to the private repo. You may also need to clean up your package-lock.json
  3. Your Font Awesome pro license is expired.You can't use the private registry anymore, not even for free packages.
Apekshagb commented 3 years ago

@tagliala thanks for the details. Quick question, we weren't having this issue until last Thursday what changed since Friday? I am unable to track any updates for the following package version that we are using in our application.

"@fortawesome/fontawesome-free": "^5.14.0" "@fortawesome/fontawesome-pro": "^5.14.0"

Also, we do have a pro package subscription and we tried to configure the latest token under the .npmrc file and we still experience the same issues. Any recommendation on this?

tagliala commented 3 years ago

Also, we do have a pro package subscription and we tried to configure the latest token under the .npmrc file and we still experience the same issues. Any recommendation on this?

Yes, please send an email to hello@fontawesome.com

I've just tried to install @fortawesome/fontawesome-free through the private repo, so I cannot replicate

Any chance that the license expired?

Apekshagb commented 3 years ago

@tagliala our license has not expired, we generated a token a few hours back and we are not able to authenticate that either. i can send an email to hello@fontawesome.com.

What details are you looking for within the email?

tagliala commented 3 years ago

What details are you looking for within the email?

Someone from the Pro support team will follow up. You can link to this discussion to provide context, but I think they will require some logs from your specific npm/yarn installation

Apekshagb commented 3 years ago

I can provide this link and also share some details.

FragsterAt commented 3 years ago

Same issue, no .npmrc file in project folder and deleted package-lock.json npm install --save @fortawesome/fontawesome-free

tagliala commented 3 years ago

Same issue, no .npmrc file in project folder and deleted package-lock.json

.npmrc can also be present in other paths

any chance to provide a log, by having care of omitting sensitive information?

The output of npm install --save @fortawesome/fontawesome-free --verbose and npm config list can be helpful.

Here it is an example of my .npmrc in a folder I use for FA Pro

$ npm config list
; "user" config from ~/.npmrc

//registry.npmjs.org/:_authToken = (protected) 
email = "" 
init.author.email = "" 
init.author.name = "Geremia Taglialatela" 
init.author.url = "" 

; "project" config from ~/dev/tests/fa5pro/.npmrc

@fortawesome:registry = "https://npm.fontawesome.com/" 
//npm.fontawesome.com/:_authToken = (protected) 

; node bin location = ~/.nvm/versions/node/v14.16.1/bin/node
; cwd = ~/dev/tests/fa5pro
; HOME = ~
; Run `npm config ls -l` to show all defaults.

And then the output of the same command in a folder I use for FA Free

$ npm config list
; "user" config from ~/.npmrc

//registry.npmjs.org/:_authToken = (protected) 
email = "" 
init.author.email = "" 
init.author.name = "Geremia Taglialatela" 
init.author.url = "" 

; node bin location = ~/.nvm/versions/node/v14.16.1/bin/node
; cwd = ~/dev/tests/fa5free
; HOME = ~
; Run `npm config ls -l` to show all defaults.
FragsterAt commented 3 years ago

@tagliala Thank you! npm config list shows additional .npmrc files, one was with old pro key, after removing it, all works.

I think, it should work with the old key, but the "pro package" version should be frozen with its expiration date, and the free package should be current