logoalt Hacker News

Show HN: Bun-sqlgen – Type-safe raw SQL for Bun, no ORM

33 pointsby ilberttoday at 2:20 PM16 commentsview on HN

Comments

giovannibonettitoday at 4:33 PM

Those looking for a more mature solution in this space will probably enjoy SQLc [1]. It was initially developed for Go applications, but over the years it got pluggins for many other languages, including JavaScript/Typescript.

[1] https://sqlc.dev/

genshiitoday at 4:31 PM

This is cool, but when the very first paragraph of the readme is clearly LLM generated, it makes me doubt the quality of the project.

show 1 reply
rankdifftoday at 4:08 PM

sqlc is worth a mention.

https://sqlc.dev

psc007today at 2:43 PM

Can you make it work/ does it work with Porsager-Postgres in modnes which buns Postgres client is «based on»?

show 1 reply
sHooKDTtoday at 2:49 PM

Nice project, thanks! I was looking for something like that for quite a while.

Any chance to get it to work with Node?

Unfortunately in my opinion and experience Bun is not really suitable for production. Does it have anything special which makes this possible?

show 2 replies
psc007today at 2:44 PM

Support for postgis?

show 1 reply
danr4today at 3:06 PM

pretty cool

ilberttoday at 2:20 PM

I write Bun.sql with raw SQL and no ORM, and the one thing I kept missing was types. You write a query, get back `any[]`, and hand-write a row type that silently drifts from the actual columns. Drizzle/Kysely fix this by moving the query into TypeScript, but then you're not really writing SQL anymore.

bun-sqlgen goes the other way. You keep writing raw SQL queries, just give each one a name.

A codegen step reads your migration `.sql` files, stands up a throwaway Postgres via PGlite (so no Docker) or SQLite, prepares every tagged query against it, and writes a `.d.ts` that maps each query name to its real result type. After that, plain `tsc` does the rest: `user.notExistingField` won't compile, and `display_name.length` gets flagged because the column is nullable.

Nullability was the annoying part. Postgres's describe doesn't hand you per-column nullability, so I infer it from the query plan plus the catalog, with manual overrides for the cases that genuinely can't be inferred. SQLite works too.

The runtime stays 100% Bun.sql, the generated file is the only artifact (commit it), and codegen is fast enough to rerun on save.

It's early (v0.1, built it for my own projects) so I'd mostly like to hear where it falls over.

show 2 replies