-
Notifications
You must be signed in to change notification settings - Fork 7
Crash when yarn's version plugin is installed #477
Comments
What's your use case for using monodeploy alongside the version plugin? They're typically mutually exclusive. Either way, it definitely shouldn't crash. I'll take a look. What version of yarn are you using? (I need to add this to the issue template 😄) I'm working on a v3 release, so I wonder if it works with the v3 pre-release. If it does, I can backport the relevant fixes. |
Sure, the version plugin is not needed. It's been just my repository setup when I tried monodeploy. I'm not happy with "version" because of what you call "implicit" dependencies. That's why I look into monodeploy, which seems pretty good (although it doesn't really work for me - that's the point of my question "how does it work"). I'm using yarn 3.2.0 (current stable). |
I can reproduce on v3:
|
Looks like the same issue as yarnpkg/berry#3857 |
I'm getting a similar error with https://github.com/mhassan1/yarn-plugin-aws-codeartifact
Comes from line |
Monodeploy has been forked under a new name Monoweave. I've copied your issue over and will address it in the monoweave project. |
Describe the bug
yarn monodeploy is crashing, when yarn's version plugin is installed.
To reproduce
yarn plugin import version
yarn monodeploy --dry-run
Expected behavior
No crash - should work
The text was updated successfully, but these errors were encountered: