The intention is to make use of the new "Origin privet file system" api, this provides the website with a sandboxed block level file system on the users device

The intention is to make use of the new "Origin privet file system" api, this provides the website with a sandboxed block level file system on the users device that can be used for efficient access and writes. It will be possible for WASM SQLite, or any other DB engine ported to WASM, to have full ACID compliance. The SQLite team have been working with browser developers to ensure the new API is sufficient to enable all this. Honestly, and I keep going on about it, SQLite in the browser via WASM is the missing piece to make "offline first" PWAs a serious contender when deciding an architecture for an app. 2023 is going to be the year of SQLite in the browser. https://webkit.org/blog/12257/the-file-system-access-api-with-origin-private-file-system/ https://webkit.org/blog/12257/the-file-system-access-api-wit... https://sqlite.org/wasm/doc/trunk/persistence.md#opfs https://sqlite.org/wasm/doc/trunk/persistence.md#opfs https://chromestatus.com/feature/5702777582911488 https://chromestatus.com/feature/5702777582911488