pnpm VS bun

We assume that Node.js and pnpm are already installed. The setup was performed on macOS, but it should work in any modern shell environment.

I think this is somewhat funny.

His comment is pretty understandable if you've done frontend work in javascript.

Node_modules is so ripe for duplicate content that some tools explicitly call out that they're disk efficient (It's literally in the tagline for PNPM "Fast, disk space efficient package manager": https://github.com/pnpm/pnpm)

So he got ok results (~13% savings) on possibly the best target content available in a user's home directory.

Then he got results so bad it's utterly not worth doing on the rest (0.10% - not 10%, literally 1/10 of a single percent).

---

Deduplication isn't super simple, isn't always obviously better, and can require other system resources in unexpected ways (ex - lots of CPU and RAM). It's a cool tech to fiddle with on a NAS, and I'm generally a fan of modern CoW filesystems (incl APFS).

But I want to be really clear - this is people picking spare change out of the couch style savings. Penny wise, pound foolish. The only people who are likely to actually save anything buying this app probably already know it, and have a large set of real options available. Everyone else is falling into the "download more ram" trap.

3) Pnpm (Space Saver & high performant)

pnpm or npm or yarn

My stack of choice is node and pnpm, but this should work for most commonly used tools.

pnpm 10

The State of JavaScript 2024 survey results GitHub Copilot is now Free Tailwind CSS 4 JerryScript 3.0 Transformers.js v3.2 Bun 1.1.39 & 1.1.40 pnpm Update ESLint v9.17.0

Pretty simple. Now, I just needed to change the code to use Playwright instead of Puppeteer and Jest. Oh, and I also wanted to use pnpm instead of npm. Here’s a link to my forked GitHub repo.

All in all, before eventually migrating to some boring modern technology, I decided to try using Bun with it instead of Node. I didn't come up with this idea completely out of nowhere; I had some interesting experience with Bun already, and the promise of zero-config development had proven to be a working approach for me. So I decided to test the hypothesis of letting Bun handle the obsolete Node project to see what it would yield.

curl https://bun.sh/install | bash

FROM php:latest # Instalar unzip RUN apt update && apt install -y unzip # Instalar Composer de outra forma, mas com o mesmo resultado RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer # Configurar as variáveis de ambiente ENV HOME="/root" ENV PATH="/root/.composer/vendor/bin:${PATH}:/root/.bun/bin" # Instalar Bun RUN curl -fsSL https://bun.sh/install | bash # Criar alguns symlinks para o executável bun RUN ln -s $(which bun) /usr/local/bin/npm RUN ln -s $(which bunx) /usr/local/bin/npx # Instalar o Laravel Installer RUN composer global require laravel/installer # Instalar a extensão pcntl RUN docker-php-ext-install pcntl

We'll begin by creating a Hono app. I'm using Bun as my package manager.

Seriously? Bun has over 500 open issues with the label "crash". https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...

The socket implementation is broken too https://github.com/oven-sh/bun/issues/5627

The framework is coming along nicely - it's built on Bun with lots of TypeScript goodness baked in. I've been running some speed tests against other JS/TS frameworks, and trust me, this thing flies! 🚀

This post shows how to embed the editor in a Bun-powered Vite project handled by Vanilla JS.

This post shows how to start to develop a Svelte 5 project with Bun.