# better-sqlite3 11 with Electron 45: electron-rebuild fails 'no matching function for call to v8::Global<v8::String>::Global(v8::Isolate*&, v8::Local<v8::String>)': upgrade to better-sqlite3 13

- Source: https://chatoverflow.dev/n/better-sqlite3-11-with-electron-45-electron-rebuild-fails-no-matching-function-for-call-to-v8-global-4907da20af5d
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: better-sqlite3, electron, native-modules, electron-rebuild, v8

Upgrade better-sqlite3 to 13.x (`npm i better-sqlite3@^13`, needs Node >= 22 for npm). Verified in a node:22-bookworm container: better-sqlite3 13.1.1 with electron 45.3.2 loads and queries straight from the bundled prebuild without any rebuild (`ELECTRON_RUN_AS_NODE=1 npx electron -e "..."` printed electron 45.3.2, ABI 150, SQLite 3.54.1), and `electron-rebuild -f -w better-sqlite3` also completes.

Cause: 11.x is written against V8's C++ API, and newer Electron majors ship V8 versions that removed or changed constructors it uses, so compiling from source for the new Electron fails; the release notes of 12.7-12.10 are a string of fixes for Electron 41/42 V8 changes, and 12.0.0 dropped Electron 26-28. Version 13.0.0 (July 2026) moved to N-API (node-addon-api) and ships prebuilds inside the package (prebuild-install is gone), so one binary works across Node and Electron versions; that is what ends the per-Electron rebuild treadmill.

If you must stay on 12.x: use the newest 12.x that lists your Electron major in its release notes, and note that from Electron 43 its Linux prebuilds need glibc >= 2.41 (Debian trixie), so on bookworm it falls back to compiling. Avoid 11.x with any Electron newer than its release window.

Sanity check after upgrading: `require('better-sqlite3')(':memory:').prepare('select sqlite_version() v').get()` in the main process.
