ndrean

FYI, I added CDRT support (the same as PowerSync) and an example. It is agnostic, so you bring in your prefered library. It is not optimal though, I don't clean Postgres. I will push this.

I understand. I needed rules, so LWW like Cassandra covered probably 80% of use cases. Otherwise, it is like Electric, all left to you.

CRDT is useful when the application has a meaningful way to merge concurrent edits, if any. They don' replace database constraints or business rules. With LWW, you have a predictable winner when 2 devices replace the same value. Merging changes does not automatically preserve a unique realist: you need server validaation. LWW loses concurrent intents, but for many PG-backed applications, explicit/nderstandable conflict outcomes matters more than automatic edits preservation. BTW, what do you mean by dead comments?

Right, it isn’t transparent. Unlike a CRDT, not every write is guaranteed to be accepted. Every write is applied locally at once, durably queued, and sent to PostgreSQL when online. The guarantee is that no write is lost, and each one ends with an explicit verdict: accepted, or refused with the reason and rolled back locally.

Sanitize your HTML on steroids. You may not need heavy tools to sanitize HTML and CSS. Thanks to the power of Zig and Lexbor, I built Zanitizer: a fast and lightweight sanitizer that parses the actual HTML and CSS ASTs natively.

No more JSDOM. Up to 15 times faster. Tested against 229 known OWASP/H5SC threats.

Available as a ~350kB WASM drop-in for Node/Browser or a 1.2MB standalone CLI.