4 ms·

I just spent a couple hours migrating my knife sharpening website backend from Bun to Node. Feels good to avoid that lock-in. I was initially gung-ho for Bun bu

I just spent a couple hours migrating my knife sharpening website backend from Bun to Node. Feels good to avoid that lock-in. I was initially gung-ho for Bun but increasingly unsure about it. Things I'll miss for sure: - Querying sqlite with tagged template literals - Bun.password.verify being argon2 is a better default - HTML imports - JSX transpilation - Auto loading .env file https://burlyburr.com https://burlyburr.com, which hits https://backend.burlyburr.com https://backend.burlyburr.com

AbuAssar 5mo ago
Node supports auto loading .env and also supports sqlite
- jpsimons 5mo ago
  Sure, but at least on Node 22 I think I have to pass `--env-file=.env` option to make it pick up .env.
  - afavour 5mo ago
    Certainly true but there’s a line between “better DX” and… well, kinda laziness
    - traderj0e 5mo ago
      Yeah I don't want it to silently read magic config files
  - AbuAssar 5mo ago
    There is also 1 line to load .env in node without passing an argument
zarzavat 5mo ago
Why not just write a small helper library to add back the features you miss? Node includes SQLite and Argon2 at least, if the issue is the interface then that is easily fixed.
- jpsimons 5mo ago
  Claude did write me a simple wrapper so I can keep using tagged template literals in the same way with Node.
tkel 5mo ago
Node supports Querying sqlite with tagged template literals. https://nodejs.org/api/sqlite.html#databasecreatetagstoremaxsize https://nodejs.org/api/sqlite.html#databasecreatetagstoremax...