Update our package manager tools

[flagrede]

The scope of this task will be solely on changing our package manager.
There is a second issue with the monorepo tool.

---

We currently have some tech debt on both our packages manager (Yarn) and our monorepo tool (Lerna)

• 2/3 major versions behind the latest yarn version. (current: 1.22.19 / latest: 3.6.3 - 4.0.0-rc.50)
• 4 major versions behind for the later lerna version. (current: 3.18.4 / latest: 7.3.0)

Regarding monorepo tools here's a good resource on the current landscape:
https://monorepo.tools/

For package management, the options are:

• mpm
• pnpm
• yarn
• bun

Here are some notes on these options.

Package Manager

Bun

Bun is a highly anticipated javascript runtime/toolkit/package manager that has been in development for some years and recently hit v1.0. When used as a package manager it provides real performance gain compared to other solutions.

Private Zenhub Image

Workspace solutions

Lerna

Private Zenhub Image

Lerna is the mono repo tool we are currently using and it's written in TypseScript. The latest version provides a lot of improvements.

Turborepo

Private Zenhub Image

Turborepo is the mono-repo solution maintained by Vercel, targeted for JS/TS projects, and written in Rust. It has good documentation, seems fairly easy to set up, and has good performance well.

https://turbo.build/repo/docs/getting-started/existing-monorepo
https://turbo.build/repo/docs/handbook/sharing-code/internal-packages

[ryanchristo]

We should further discuss this on our standup tomorrow and maybe include in the current sprint.

[ryanchristo]

Per architecture call, a couple things to consider when we start trying out some of these alternatives:

• consistency of tooling across our typescript repositories would be nice, so we would start with regen-web but keep in mind compatibility of the package manager with both netlify and heroku (we previously had issues with pnpm and heroku when prototyping the origination app)
• we also use lerna for releases, we could replace this incrementally or continue using lerna for releases

[ryanchristo]

This issue will be focused on using bun and the workspace will be a separate issue.

[ryanchristo]

Hey team! Please add your planning poker estimate with Zenhub @blushi @flagrede @ryanchristo @wgwz

[blushi]

This issue will be focused on using bun and the workspace will be a separate issue.

@flagrede could you update the issue title/description accordingly and create the follow-up issue for managing the monorepo separately? thanks

[flagrede]

Some updates on this task:

• we currently can't use bun because it doesn't support monorepo and hoist all dependencies at the top root node_modules (related issue github.com/Monorepo support oven-sh/bun#533)
• we would still benefit from upgrading either to the latest yarn or npm instead (here's a document on that for yarn: https://yarnpkg.com/migration/overview)
  For both npm and yarn we would need to upgrade nodejs first, here's the issue for doing that: https://app.zenhub.com/workspaces/rnd-dev-team-5f8998bec8958d000f4609e2/issues/gh/regen-network/rnd-dev-team/1803
  Yarn requires Node 18+
  NPM version is also depending on nodejs version: https://nodejs.org/en/download/releases

[flagrede]

Update 2:
I was able to make Bun work in our monorepo! There were several issues that misled me yesterday, like different react versions installed at the same time that were breaking the compilation.
So locally we’re ready, but Bun is not (yet) supported by Netlify but should be soon (https://answers.netlify.com/t/install-and-build-with-bun/101727/12). I’ll put the PR on hold in the meantime.