-
Notifications
You must be signed in to change notification settings - Fork 19
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
Design scheme for fetching yarn dependencies from arbitrary registries #64
Comments
Some experimentation: Redhat's lock-treatment-tool doesn't do what we need because its behavior can't be made scope-specific. Perhaps we can upgrade it to support scoping. Running |
That didn't work either. |
It appears that we need to edit
which we can use to make an edit like this:
Some testing suggests this works. Next step is to create some tooling to automate the process. |
Success. This works:
|
Currently yarn stores the host name used to fetch dependencies in
yarn.lock
. Sinceyarn.lock
is in the git repo, this effectively prevents decentralized builds (see: yarnpkg/yarn#2566 and yarnpkg/rfcs#64). We need to devise some method for overriding the host name inyarn.lock
so our users can build packages using their npm registry of choice.The text was updated successfully, but these errors were encountered: