Skip to content

Specify yarn classic as PM for js-sdk wrapper#226

Merged
t3chguy merged 1 commit intomainfrom
t3chguy-patch-3
Feb 17, 2026
Merged

Specify yarn classic as PM for js-sdk wrapper#226
t3chguy merged 1 commit intomainfrom
t3chguy-patch-3

Conversation

@t3chguy
Copy link
Member

@t3chguy t3chguy commented Feb 17, 2026

Continuation of #225

Without this, in CI, js-sdk downstream tests fail due to complement-crypto being checked out within matrix-js-sdk, and thus inheriting its packageManager definition of pnpm

Copy link
Member

@richvdh richvdh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM otherwise

"vite": "^5.4.21"
}
},
"packageManager": "yarn@1.22.22"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we have to pin it to a specific version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn classic 1.x behaves extremely differently from yarn berry 4.x so I recommend doing so even if it is not necessary. The yarn.lock is generated by yarn classic, so using yarn berry would make an incompatible lockfile. https://github.com/matrix-org/complement-crypto/blob/main/internal/api/js/js-sdk/yarn.lock#L2

@t3chguy t3chguy merged commit 52bbf25 into main Feb 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments