15:I[981,["658","static/chunks/658-a698693f56d0116a.js","183","static/chunks/183-6beeeb801c274aaa.js","474","static/chunks/app/%5Btype%5D/layout-631c4730b83c8223.js"],"Posts"] 16:T4d8,I built web-sqlite-js because I wanted an "out-of-the-box" way to use SQLite WASM with persistence.

While the official SQLite WASM build is excellent, setting it up with the Origin Private File System (OPFS), handling the Web Worker communication, and ensuring concurrency safety (Mutex) involves a fair amount of boilerplate.

This library handles: - *Worker Orchestration*: Spawns and manages the SQLite worker. - *Persistence*: Automatically uses OPFS for file storage. - *SharedArrayBuffer Support*: Required for high-performance VFS. - *Safe Concurrency*: A built-in Mutex ensures that SQL commands and transactions are executed sequentially even if called concurrently from the main thread.

It’s designed for "local-first" apps where you want the reliability of a relational database without needing a backend for every query.

GitHub: https://github.com/wuchuheng/web-sqlite-js Docs: https://web-sqlite-js.wuchuheng.com

I'd love to hear your thoughts on the approach or any feedback on the API design.17:T6b7,This weekend I started building Iconoma because I kept hitting the same problem across projects:

Icons slowly turn into a junk drawer. Random SVGs with inconsistent sizes, weird fills, different naming, different optimization rules, and every app/team ends up re-solving the same cleanup work. The result is death by a thousand tiny UI cuts.

My vision: icons should be boring infrastructure — one source of truth, deterministic outputs, zero “why is this icon different?” surprises.

## What Iconoma does

- Imports and organizes icons with consistent naming + tags - Runs SVGO with your customizabl

A Message from AI Research Leaders: Join Us in Supporting OpenReview