-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support for yarn@>=2.0.0 #4
Comments
I am willing to try this and open a PR. I wanted to verify first if it would be accepted and if there are any items I should be aware of to contribute. I do not see a contributor's guide, so I thought I would ask prior to doing any work. Thanks! |
If you're down for it, please feel free to give it a try! Hit me on Teams and we can chat about the contibution stuffs, it's still early in this project's life. Still working on the publishing flows, etc, but definitely excited to collaborate. |
Hi, any updates on this issue? I'm also running into this problem when trying to adopt yarn 4. Currently have to workaround with solution mentioned here: yarnpkg/berry#316 (comment) It would be great if we can use this tool to improve dev experience! Happy to contribute to help as well if needed :) |
Since yarn >=2.0.0, yarn no longer uses or respects either the
.npmrc
file or.yarnrc
. Instead, it stores its configuration in a YAML file,~/.yarnrc.yml
. Supporting an streamlined way to obtain necessary authentication for Azure DevOps registry feeds for yarn@>=2.0.0 would be greatly appreciated.The text was updated successfully, but these errors were encountered: