Yep, yep, I understand the reasons. That's why in where I work we decided to use asyncify because COOP is very strict for us It has a penalty on cold start, but once many blocks cached it works perfectly, without event loop interruptions
Btw, I still see one problem of official SQLite solution — it requires COOP to use ( https://web.dev/i18n/en/coop-coep/ ). It is a pretty annoying restriction. For example, you will not be able to use iframe to other resources(like embed youtube video). COOP is needed due to SharedArrayBuffer usage.
wa-sqlite can work without COOP, but it is under GPL, unfortunately. It don't allow using it in private codebase without open-sourcing the project
I am preparing for this! Building Kikko[0] that widely supports all the of platforms that have SQLite on it, and allows building reactive interface on top of React/Vue/AngularJS(WIP)/whatever.
Here is the code example for react: https://kikko-doc.netlify.app/react-integration/installation.
Some technical details: with special sql`INSERT INTO ${sql.table`some-table`}` syntax, it tracks in which tables changes are happened, and notify other tabs to make refetch to the subscribed tables.
Project is in alpha, and already has support of absurd-sql, wa-sqlite for web; expo, tauri, electron, ionic, React Native.
I am super excited to add support of official SQLite wasm implementation