Skip to content

WIP: Move from npm to yarn #208

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

WIP: Move from npm to yarn #208

wants to merge 1 commit into from

Conversation

pastelsky
Copy link
Contributor

@pastelsky pastelsky commented Mar 19, 2025

Not ready for review yet.

Usually this sort of thing wouldn't matter — I thought npm's caught up a bit with yarn.
But turns out its still pretty bad when installing fat packages. I was trying to experiment getting @atlassian/editor into the extension,
and at the moment npm takes a good 10+ minutes to npm install @atlassian/editor-core .
It takes several more minutes to run things like npm dedupe (been running for > 20 mins now).

Moving from npm to yarn essentially seems like a blocker for any reasonable devloop to work with editor core.

This is still in draft because it likely requires the extension to be sanity tested once and builds to be fixed.

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.

1 participant