-
I'm migrating a Yarn v1 project that uses private scoped packages. The project is first setup to create an @<scope_name>:registry:https://private.registry.com/
//private.registry.com//:_password=<base64 encoded authentication token>
//private.registry.com//:[email protected]
//private.registry.com//:[email protected]
//private.registry.com//:always-auth=true I assumed I have to use npmRegistries and npmScopes in my configuration like so: nodeLinker: node-modules
npmRegistries:
//private.registry.com:
npmAlwaysAuth: true
npmAuthIdent: "[email protected]:<base64 encoded authentication token>"
npmScopes:
<scope_name>:
npmRegistryServer: https://private.registry.com/
yarnPath: .yarn/releases/yarn-berry.cjs But when I run
How can I migrate Yarn: v2.4.1 Thank you :) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Can you try base64'ing your whole ident? Cf this similar thread: #316 (comment) If it's this, we probably should help detect the problem. |
Beta Was this translation helpful? Give feedback.
-
If you run
You can use just npmScopes:
<scope_name>:
npmRegistryServer: https://private.registry.com/
npmAlwaysAuth: true
npmAuthIdent: "[email protected]:<base64 encoded authentication token>" |
Beta Was this translation helpful? Give feedback.
Can you try base64'ing your whole ident? Cf this similar thread: #316 (comment)
If it's this, we probably should help detect the problem.