Great watch but to summarize:
-
Bun beats Node/Yarn for package installation
-
Somewhat better API/DX in some ways.
-
Loses poorly in testing performance
-
Tons of incompatibility issues/performance issues in other areas.
General summary: Just don’t use Bun yet, seems like it needs some more time in the oven.
I’m with the parent poster. How often is it hindering your work?
It’s at tops, a 15-30 second wait, usually done at the start of the project.
I’m a unique use ase, where I have about 10 projects (because microservices) that I’d have to npm install, and it’s still not a pain to install them.
Are people running npm install dozens of times a week on the same project? Because why?
I’m not shitting on Bun. I’m actually supporting it’s growth. But until it solves some real performance bottlenecks, (switching from gulp/webpack to vite changed our compiling time from 18 seconds to 2 seconds), I can’t see any reason for people to change their workflow.
It’s at tops, a 15-30 second wait
First: it can be a lot longer than 15-30s. One project I work on takes around 90s for a fresh install. This used to be worse in older versions of npm, and it’s worse on Windows.
Second: it also affects things like CI/CD. I prefer using Yarn 2+ for that reason (all dependencies are stored as part of your repo). It might not sound like much, but 30 extra seconds does decrease your productivity more than you might think if you have to wait for it every single time.
