yarnpkg / berry

📦🐈 Active development trunk for Yarn ⚒
https://yarnpkg.com
BSD 2-Clause "Simplified" License
7.45k stars 1.11k forks source link

[Bug] Cannot access private registry #2409

Closed Lonli-Lokli closed 3 years ago

Lonli-Lokli commented 3 years ago

Describe the bug

I am trying to incorporate private nom registry from Infragistics (https://www.infragistics.com/products/ignite-ui-web-components/web-components/components/general-licensing.html#access-token-usage) Specifying just AUTH_TOKEN was not enough - seems like they, same as Frog, requires email. I found this comment on how can I actually copy token https://github.com/yarnpkg/berry/issues/1039#issuecomment-597656354 1) The problem is that when I run yarn npm login --scope infragistics - root .yarnrc.xml is not created so I cannot see it 2) Even after successful log-in I still not able to install this scoped package, getting yarn  ✔  1178  08:06:47 ➤ YN0000: ┌ Resolution step ➤ YN0041: │ @infragistics/igniteui-angular@npm:11.0.12: Invalid authentication (as an anonymous user) ➤ YN0000: └ Completed in 0s 859ms ➤ YN0000: Failed with errors in 0s 865ms

To Reproduce

I do not know how to let you reproduce it - it's all about private registry Here I my project .yarnc.yml yarnPath: ".yarn/releases/yarn-berry.cjs" nodeLinker: node-modules

npmScopes: infragistics: npmRegistryServer: "https://packages.infragistics.com/npm/js-licensed/" npmAlwaysAuth: true

Environment if relevant (please complete the following information):

yarnbot commented 3 years ago

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

Eli-Black-Work commented 3 years ago

See my answer at https://github.com/yarnpkg/berry/issues/1039#issuecomment-827417634 🙂