Launched this week
bunpm
npm, yarn, pnpm - same commands, powered by Bun underneath
7 followers
npm, yarn, pnpm - same commands, powered by Bun underneath
7 followers
bunpm is a transparent wrapper that intercepts npm, yarn, and pnpm commands and runs them through Bun — without changing anything about how you work. Keep using npm install, yarn add, pnpm add exactly as before, just 10-25x faster. Output is formatted to match the tool you called, so nothing looks different either. Your original npm, yarn, and pnpm are never modified. Fully reversible. Cross-platform: Windows, macOS, Linux.
Love this, the whole "drop-in and forget about it" angle is exactly what I'd want. One thing that would make it even better for me: a small built-in benchmark command like `bunpm bench` that runs a representative install and prints the time savings versus the original tool, so I can actually see the speedup on my own projects instead of just trusting the 10-25x claim.
@berivan242280 Love this idea 'bunpm bench' as a built-in command that runs a real install and prints actual time vs estimated npm time. Adding it to the v3 list, thamks for the concrete suggestion!
honestly this looks super useful, love that it's fully reversible. one thing though, could you add a way to see the actual time saved per command, like a small "this would've taken 14s with npm" at the end of each run. would make it way easier to show the team why we should adopt it
@hakanbaayaqrjy That "would've taken x sec" message at the end of each run is a great idea, makes the value visible without changing anything about the workflow. On the roadmap for sure.
finally something that lets me keep my muscle memory. ran a fresh install on a node project and it was noticeably snappier, plus the output looked identical to regular npm so nothing in my terminal muscle memory broke.
@ld_ilayda57147 This is exactly what bunpm was built for-snappier installs,zero learning curve.glad the output felt native.
the fact that you format output to match whichever tool you called is honestly such a thoughtful detail, like you didn't have to do that but it makes the switch feel basically invisible. smart move
@ezels5ii That detail was important to get right - if yarn add printed npm style output it would feel broken even if it worked. Thanks for noticing.