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

having problems with dev environment setup #671

Closed
maraoz opened this issue May 14, 2022 · 4 comments
Closed

having problems with dev environment setup #671

maraoz opened this issue May 14, 2022 · 4 comments

Comments

@maraoz
Copy link
Contributor

maraoz commented May 14, 2022

Hi! I'm following the README's guide for project setup, and I'm stuck with the https://github.com/yearn/yearn-finance-v3#yearnweb-lib-access section.

I've created the Github Personal Access Token as described in the guide, but I'm getting

error An unexpected error occurred: "https://npm.pkg.github.com/download/@yearn/web-lib/0.2.27/a5aec6437505213aef6fb84cf564053246dd21b7cb0105c33c517bfe872ed3bc: Request failed \"401 Unauthorized\"".

every time I run yarn install -- no matter what premissions I assign to the token.

Two questions:

  1. what permissions are required for the gh personal access token for yarn install and yarn dev to work?
  2. does someone from yearn need to give me read acces to @yearn/web-lib, or is this a misconfiguration on my end?

Thanks in advance!

@maraoz
Copy link
Contributor Author

maraoz commented May 14, 2022

I should clarify that when I run npm config get npm.pkg.github.com/:_authToken, I see my personal access token printed in my shell, so I seem to have configured the .npmrc correctly

@xgambitox
Copy link
Contributor

Hey there @maraoz ! sorry readme is not clear enough, this web-lib dependency was introduced recently. Please follow this instructions.

The permissions needed in the personal access token are described here

If you are able to set it up properly, please feel free to update the README :)

@maraoz
Copy link
Contributor Author

maraoz commented May 14, 2022

thanks @xgambitox ! I had just fixed it myself by including the access token config in the .npmrc for this repo (not the global one). I'll update README next. thanks!

@maraoz maraoz closed this as completed May 14, 2022
@xgambitox
Copy link
Contributor

@maraoz just be aware that by including the PAT in the file inside the repo rather in the global home directory, there is a high risk of pushing the token to the public repo in github, which is not ideal.

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

2 participants