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
Migrate from Yarn / Lerna to pnpm #543
Comments
It's better do this after I finish merging the |
As a reference, oxc-resolver is already using pnpm and it seems to have no problem: https://github.com/oxc-project/oxc-resolver/blob/main/.github/workflows/release_napi.yml |
It pnpm's publish/release flow anywhere near as good as lerna's? That's pretty much why everyone still uses lerna. |
Most package managers have similar features, and the choice should mostly depend on what most contributors are comfortable with. Personally, I use a yarn modern and changesets in my projects, and have been happy with. |
@underfin Done in #545. I update the napi-rs cli to Commands related to releasing should be no problems, but you might want to checkout out them again. |
Let me know if some assistance is required with this, I've ported a couple of projects from Yarn to PNPM, I'd be willing to take this on if that helps.
Should be pretty decent, are there any specific Lerna features you need that are not in PNPM? |
I'm looking into this. |
The migration is finished in #567. But there are some other problems left:
|
Side note, you can also use Lerna-Lite with pnpm and |
Lerna was used for legacy reasons but is actually no longer necessary.
Yarn was also used for legacy reasons - old versions of pnpm had issues in Docker, but should no longer be an issue according to @Brooooooklyn. We should investigate whether moving to pnpm would improve CI time.
The text was updated successfully, but these errors were encountered: