Proof

expo-sqlite

real upstream package — not intercepted. its JS (openDatabase*, SQLiteDatabase, SQLiteStatement cursors, SQLiteProvider, kv-store, tagged queries) runs from the bundle over the ExpoSQLite native module (native-seams/expo-sqlite.ts), which follows ios/SQLiteModule.swift on the shared bedrock-sqlite WASM engine: the per path database cache, lazy sqlite3_step cursors, iOS error codes and messages. databases live under Documents/SQLite in the tenant memfs and persist to IDB; the seam loader waits for the engine so the sync api is ready when the bundle evaluates.

90%

API coverage

No visual proof cases have been published for this package yet. The registry summary below describes what the compat layer implements.

Working (14)

open/close (cached by path and options, ref counted)execpreparerun with array and named bindingsstepgetAllresetfinalizecolumn namesisInTransactionwithExclusiveTransactionAsync (second connection)deleteDatabaseimportAssetDatabaseAsync from a fileserialize (VACUUM INTO) and deserialize

Missing (2)

onDatabaseChange never fires (no sqlite3_update_hook in bedrock); backupsessions and loadExtension throw; database files are not visible to expo-file-system