Discuss: Should bun should be installed on system

[publicJorn]

Currently the project assumes that bun is installed on the system globally.

Would it not be better to install it as a package? Is that even possible?

I'm ok with setting bun as standard withing IGNE. But we should clearly communicate that to the employees and actively update existing projects.

What are your thoughts @maanlamp?

[igne-wouter]

Because we (partially) ported this template from Chippr — where we used Bun — this also runs on Bun.

I'm not opposed to using other tools, but Bun has shown itself to be the fastest to run anything we needed (and waiting for code to compile is a major nuisance for me).

As for the installation: I'm of the opinion that all dependencies should be explicitly included in package.json, but the manager isn't really a dependency so I'm not sure how to approach this. NodeJS has created corepack for this, with the "packageManager" field in package.json, but they don't "support" Bun yet (it's experimental so no manager is "supported", really).

I really like Bun over any other manager, as it's proven itself the fastest (and for personal projects, most versatile) package manager and build tool. I'm thus in favour of switching to Bun for all projects at Igne. For the time being, we'd have to just enforce a local install, I guess.