Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Deploying App with FortAwesome Pro Packages #15920

Open
1 of 4 tasks
mackenzienolan opened this issue Dec 9, 2019 · 8 comments
Open
1 of 4 tasks

Issue with Deploying App with FortAwesome Pro Packages #15920

mackenzienolan opened this issue Dec 9, 2019 · 8 comments

Comments

@mackenzienolan
Copy link

mackenzienolan commented Dec 9, 2019

Describe the bug
When working locally there are no issues, however when deploying via Heroku receive the following error.

error An unexpected error occurred: "https://npm.fontawesome.com/@fortawesome/pro-light-svg-icons/-/5.11.2/pro-light-svg-icons-5.11.2.tgz: Request failed \"401 Unauthorized\"".

yarnrc
"@fortawesome:registry" "https://npm.fontawesome.com/EDITED_BY_TAGLIALA"

Here is the entire source error from the build
remote: Compressing source files... done. remote: Building source: remote: remote: -----> Node.js app detected remote: remote: -----> Creating runtime environment remote: remote: NPM_CONFIG_LOGLEVEL=error remote: NPM_CONFIG_ENV=development remote: NPM_CONFIG_PRODUCTION=false remote: NODE_VERBOSE=false remote: NODE_ENV=production remote: NODE_MODULES_CACHE=true remote: remote: -----> Installing binaries remote: engines.node (package.json): >=8.15.1 remote: engines.npm (package.json): >=3.10.10 remote: engines.yarn (package.json): unspecified (use default) remote: remote: Resolving node version >=8.15.1... remote: Downloading and installing node 13.3.0... remote: Bootstrapping npm >=3.10.10 (replacing 6.13.1)... remote: npm >=3.10.10 installed remote: Resolving yarn version 1.x... remote: Downloading and installing yarn (1.21.0)... remote: Installed yarn 1.21.0 remote: remote: -----> Restoring cache remote: Cached directories were not restored due to a change in version of node, npm, yarn or stack remote: Module installation may take longer for this build remote: remote: -----> Installing dependencies remote: Installing node modules (yarn.lock) remote: yarn install v1.21.0 remote: [1/4] Resolving packages... remote: [2/4] Fetching packages... remote: error An unexpected error occurred: "https://npm.fontawesome.com/@fortawesome/pro-light-svg-icons/-/5.11.2/pro-light-svg-icons-5.11.2.tgz: Request failed \"401 Unauthorized\"". remote: info If you think this is a bug, please open a bug report with the information provided in "/tmp/build_fff20a716996bc667445e02750b3f1ac/yarn-error.log". remote: info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Expected behavior
Expected behavior is that it would deploy. This issue only started to occur a few days ago. Never been an issue in the past. I have attempted to re-deploy older code and the same issue persists.

Version and implementation
"@fortawesome/fontawesome-free": "^5.5.0", "@fortawesome/fontawesome-free-brands": "^5.0.13", "@fortawesome/fontawesome-free-regular": "^5.0.13", "@fortawesome/fontawesome-svg-core": "^1.2.0-7", "@fortawesome/free-brands-svg-icons": "^5.5.0", "@fortawesome/free-regular-svg-icons": "^5.5.0", "@fortawesome/free-solid-svg-icons": "^5.5.0", "@fortawesome/pro-light-svg-icons": "^5.7.2", "@fortawesome/pro-regular-svg-icons": "^5.7.2", "@fortawesome/pro-solid-svg-icons": "^5.7.2", "@fortawesome/react-fontawesome": "^0.1.3",

  • SVG with JS
  • Web Fonts with CSS
  • SVG Sprites
  • On the Desktop

Bug report checklist

  • [Y ] I have filled out as much of the above information as I can
  • [N ] I have included a test case because my odds go way up that the team can fix this when I do
  • [ Y] I have searched for existing issues and to the best of my knowledge this is not a duplicate
@tagliala
Copy link
Member

Hi!

Thanks for being part of the Font Awesome Community.

You have inadvertently disclosed your secret api token, please send an email to hello@fontawesome.com explaining your problem and put a link to this github issue.

I've edited your post, but someone else could have seen the key.

Please notice that we have recently changed how the .npmrc file should look like: https://fontawesome.com/how-to-use/on-the-web/setup/using-package-managers#installing-pro

@mackenzienolan
Copy link
Author

@tagliala I have done it that way, with the same result. Works locally, I get the 401 error upon deployment.

@diegomendezp
Copy link

Hi @mackenzienolan have you finally fixed the problem? I'm having the same issue with "@fortawesome/fontawesome-pro": "^5.12.0".

@drptbl
Copy link

drptbl commented Feb 27, 2020

Same issue here on GitLab while using .yarnrc.

@tagliala
Copy link
Member

@drptbl please try .npmrc

@tagliala
Copy link
Member

@drptbl
Copy link

drptbl commented Feb 27, 2020

@tagliala Thanks, I know it works with .npmrc and that's what I'm using now but I would like to use .yarnrc only and the issue is about .yarnrc.

@tagliala
Copy link
Member

@drptbl please keep using .npmrc.

If we manage to find a way to use .yarnrc (without the token being leaked in the yarn.lock file), we will add instructions to our docs

Ref: #16156

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants