Repository navigation
chore(deps): Upgrade NitroSQLite from 9.8.3 to 10.2.0 #102424
Description
Summary
Upgrade react-native-nitro-sqlite from 9.8.3 to the latest release, 10.2.0.
This builds on chore(deps): Update NitroSQLite from 9.6.0 to 9.8.0, whose PR, chore(deps): Update NitroSQLite to 9.8.2, is merged.
Why update
- Prepared statements.
db.prepare(query)prepares SQL once and runs it many times with new parameters. #294 - Independent DB connections.
open({ name, connection: 'independent' })opens a separate native connection with its own queue, so a reader can run while a writer holds a transaction. #364 - Performance improvements.
- Async queries, batches, and file imports enter a per-connection native queue without waiting for the previous result to return through JavaScript. #369
- Grouped batch parameters reuse a prepared statement, and query results skip an extra native row copy. #387
- Each connection caches its 32 most recently used statements, async work runs on a dedicated worker thread per connection, and Android writes use
fdatasync()and batch atomic writes where supported. #440
- Node.js mock.
react-native-nitro-sqlite/mockruns against better-sqlite3 for tests that need a real SQLite engine. #395
See the full comparison for every change.
Scope
- Bump
react-native-nitro-sqliteto10.2.0in App, and in the HybridApp lockfile via Mobile-Expensify#14179. - Update the optional NitroSQLite peer dependency range in react-native-onyx to
^10.2.0via feat(storage): use NitroSQLite 10.2 connections and statements. Onyx currently allows only9.x, so installing NitroSQLite 10 fails dependency resolution. - Rebuild the native apps. Upstream notes these upgrade changes:
- Existing single-connection calls keep working. Independent connections are opt-in and require
SQLITE_THREADSAFEto be non-zero. - Deleting a database now fails while another connection still uses the file.
- Prepared statements must be finalized before their connection closes.
- A SQL string with more than one statement now throws instead of running only the first statement. #439
- Query results are plain objects, not Nitro
HybridObjects, so they no longer havedispose(),equals(),toString(), orname. #440
- Existing single-connection calls keep working. Independent connections are opt-in and require
Activity
chrispader commentedon Oct 12, 2026
@MelvinBot could you assign an Expensify engineer and C+ on this issue and the related PRs?
chrispader commentedon Oct 12, 2026
@MelvinBot also update the issue to
v10.2.0MelvinBot commentedon Oct 12, 2026
I picked the engineer and C+ who handled the 9.8.x update. NicolasBonet was the engineer on chore(deps): Update NitroSQLite from 9.6.0 to 9.8.0, and ikevin127 reviewed its PR as C+.
react-native-onyx, so you need to request their reviews yourself.view run
[-]chore(deps): Upgrade NitroSQLite from 9.8.2 to 10.0.0[/-][+]chore(deps): Upgrade NitroSQLite from 9.8.3 to 10.2.0[/+]MelvinBot commentedon Oct 12, 2026
I updated the issue to target NitroSQLite
v10.2.0.mainalready uses9.8.3, so the starting version changed too.HybridObjects.view run
NicolasBonet commentedon Oct 19, 2026
@chrispader could you please let me know how much is pending to complete this?
chrispader commentedon Oct 19, 2026
I have still to address the latest review comments by @ikevin127 and @fabioh8010 and finalize my benchmark results for this Onyx change in Expensify/react-native-onyx#851 (review)
After the Onyx PR is merged, i'll ping you on the E/App PR 🙌🏼
NicolasBonet commentedon Oct 26, 2026
@chrispader same question for this week 😅
chrispader commentedon Oct 26, 2026
@NicolasBonet all issues are addressed and benchmarks were positive! We have to wait for prior Onyx bump PRs #102135 & #103208 to be merged, after that i'm going to resolve conflicts, do a last check and then we're good to go!
NicolasBonet commentedon Oct 26, 2026
Thank you @chrispader 🙏