Replies: 1 comment
-
From my understanding, it is preferred to run this logic as a custom plugin. I think the following logic can be supported:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In my case, I have created a scaffolding tool, something that is inspired by Angular CLI. Where we have one
bin
definition.The main reason for looking into Yarn, is the support of
git+ssh
package installations with the support of workspace (e.g.git+ssh://[email protected]:<workspace>/<project>git#workspace=<sub-project>
).I believe global packages are no longer possible in Yarn V3, and instead it is recommended to use the
dlx
command. Am I correct to say this does not support thegit+ssh
protocol?I think the following command would be great, if supported:
yarn dlx git+ssh://[email protected]:<workspace>/<project>git#workspace=<sub-project>
. In this case, a permanent install/alias would make this event more user-friendly.The current workaround is to clone the repository (for example in
/usr/local/lib/node_modules/
),yarn install
, and create a symlink (in/usr/local/bin/
). This allows me (with the correct shebang) to call it as any other binary.How is this use-case currently handled by the community, or is this a too uncommon use-case?
Update: See some discussion about this in #821, but not much conclusive
Beta Was this translation helpful? Give feedback.
All reactions