PGlite

“You can have normal vitest tests testing your postgres functions with in-memory pglite.”

“Yeah pglite is exquisite. Now I don't have to write separate code for client and server side queries.”

“PGlite offers the "real database" compiled to WASM, which can then be embedded similarly to SQLite.”

“Loads of useful things in the pipeline: multi connection support, native library, extensions and many more ideas.”

“The key was NOT using that environment to run the SQLx validation”

“but only in javascript/WASM”

“I am quite happy that they added support for extensions though”

“It’s a really solid piece of work. If the concurrency model fits what you’re doing I wouldn’t hesitate to use it in production.”

“I use pglite for unit/integration tests and it's been fantastic.”

“Loved how speedily I could have a "real" postgres instance without spinning up docker.”

“while it's great someone made that, it's definitely not the same”

“This sounds fantastic for running local "unit"/integration tests.”

“I really really really wish SQLite or PGLite supported multiple writers”

“PGlite would be perfect if only it allowed multiple writer connections”

“That way you don't need any specific SGQLite vs Postgres behavior switches.”

“It worked fine and made it pretty easy to spin up a development/CI environment anywhere you want.”

“From what I’ve read there’s a pretty sizable performance gap between SQLite and pglite (with SQLite being much faster).”

“With a simple `npm install` you now have a PostgreSQL instance in your web or node app”

“For most purposes, it works perfectly fine, but with two main caveats”

“because it lets me use all the postgres features”

“Starting out with postgres if done via pglite and similars with golang's sqlite-ish approach can be brilliant”

“run your backend tests against this in memory and tests can be run in parallel”

“describes memory leaks, minute-long db startup time, and huge slowdowns with live queries”

“PGlite is fantastic. I use it for my in-browser PostgreSQL server for development.”

“This is a lot faster and more convenient than spinning up a container.”

“It's been great for allowing users to generate large amounts of their own isolated data”

“since it ONLY works in Wasm, that seemed way too niche”

“The ability to .clone() the database to create "checkpoints" is also great for tests, as we can run all of the migrations and return to that clean state between each test.”

“One thing this (and any browser-embeddable data store) are fantastic for is vibe coding interactive prototypes for user research.”

“Having something like this, that I can quickly spawn and know, I am getting exact behavior as prod database would be a lifesaver!”

“real Postgres, zero container overhead, easy to spin up isolated instances per test”

“this has big potential for local-first”

“There are a few people using it in prod for customer facing web apps.”

“it feels like a sweet spot between in-memory SQLite and spinning up a full Postgres instance”

“It's now used by a huge number of developers for running local dev environments”

“we have seen enormous growth in devtools and developer environments”

“It's not as nice as transactionally isolated testing, but it's a fine replacement until I have time to replicate it.”

“Imagine being able to go from 'embedded' to 'networked' without having to change any SQL or behavior, so cool.”

“This solves the first and has potential to help with the second.”

“that's what I've been using to write "unit" tests connected to a "real" database.”