You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as I converted the dep package to yarn - it worked fine. I have to assume this is a bug.
Totally guessing, but in https://github.com/yarnpkg/berry/blob/master/packages/yarnpkg-core/sources/scriptUtils.ts
the PackageManager enum has pnpm in it. But later on in the code the workflows map variable has no entry for pnpm in it - which appears to be the issue and why it emits the error: Assertion failed: Unsupported workflow.
To reproduce
Create a Yarn Berry repo (3.2.0)
Try to yarn add a dependency from a private github repo which itself uses pnpm as it's package manager
Witness failure to import with Assertion failed: Unsupported workflow error
Self-service
Describe the bug
Using yarn 3.2.0
Unable to install a dependency from a private github repo that itself uses pnpm as it's package manager. This worked fine in yarn 1.*.
command used:
yarn add <package-name>@[email protected]:<org-name>/<package-name>.git#<branch-name>
As soon as I converted the dep package to yarn - it worked fine. I have to assume this is a bug.
Totally guessing, but in
https://github.com/yarnpkg/berry/blob/master/packages/yarnpkg-core/sources/scriptUtils.ts
the PackageManager enum has pnpm in it. But later on in the code the workflows map variable has no entry for pnpm in it - which appears to be the issue and why it emits the error:
Assertion failed: Unsupported workflow
.To reproduce
yarn add
a dependency from a private github repo which itself uses pnpm as it's package managerAssertion failed: Unsupported workflow
errorEnvironment
Additional context
No response
The text was updated successfully, but these errors were encountered: