What is `node:sqlite`, Node's built-in SQLite module?

Q: What is `node:sqlite`, Node's built-in SQLite module?

**Target Audience:** Engineers preparing for Node.js interviews — assumes basic SQL and module familiarity. **Difficulty:** Medium > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Everything below was **executed against Node v24.19.0**, where the module required cleanly with no install step. ## 1. Why This Even Matters — A Story First For years, wanting a database inside a small Node script meant a decision before you had even started: pull in a package, pick a version, decide between a callback API and a promise-wrapped one, and hope it still builds against whatever Node version your CI uses next month. Node quietly removed that decision for the common case. A database driver now travels inside the runtime itself. ## 2. The Core Idea 📌 **Interview term: node:sqlite ** — a built-in module giving Node a **SQLite** database with no npm dependency. Introduced experimentally in Node 22 and matur

The problem

Question presented to candidate: "You need a local database for a small tool and do not want to add a dependency. What does Node give you now?"

What a strong answer should cover:

node:sqlite is a built-in module — introduced experimentally in Node 22, stabilising further in later releases — that gives you a SQLite database with zero npm dependency.
Its API is synchronous: DatabaseSync and StatementSync run queries and return results directly, no promises, no callbacks — a deliberate design choice matching SQLite's own embedded, single-process nature.
That makes it a natural fit for CLIs, build scripts, local caches, and tests — anywhere a small embedded database is useful and pulling in better-sqlite3 or a full ORM would be overkill.
It is not a general replacement for a real client-server database (Postgres, MySQL) in a multi-instance production service — SQLite's file-based, single-writer model does not fit that shape.
Being labelled experimental in some Node versions matters for production use: check the exact stability level of the Node version you are targeting rather than assuming it is fully stable everywhere.
The synchronous API is the headline trade-off to name: it blocks the event loop for the duration of the query, same as any synchronous file I/O — fine for small local operations, wrong for a hot request path serving concurrent users.

Clarifying questions expected:

"Is this for a single-process tool or a concurrently-accessed service?" — decides whether the synchronous model is appropriate.
"Which Node version, and is the feature still experimental there?"

Code / implementation expected: Optional. A short synchronous query against an in-memory database is the clearest demonstration.

node:sqlite
database
sqlite
built-in-modules

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for Node.js interviews — assumes basic SQL and module familiarity. Difficulty: Medium

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Everything below was executed against Node v24.19.0, where the module required cleanly with no install step.

1. Why This Even Matters — A Story First

For years, wanting a database inside a small Node script meant a decision before you had even started: pull in a package, pick a version, decide between a callback API and a promise-wrapped one, and hope it still builds against whatever Node version your CI uses next month.

Node quietly removed that decision for the common case. A database driver now travels inside the runtime itself.

2. The Core Idea

📌 Interview term: node:sqlite — a built-in module giving Node a SQLite datab

The solution is hidden so you can try first

6 min read · 10 sections

Read the code

JavaScriptA synchronous query against an in-memory database, no dependency

const { DatabaseSync } = require("node:sqlite");

const db = new DatabaseSync(":memory:");
db.exec("CREATE TABLE users (id INTEGER, name TEXT)");
db.prepare("INSERT INTO users (id, name) VALUES (?, ?)").run(1, "Ada");

const rows = db.prepare("SELECT * FROM users").all();
console.log(JSON.stringify(rows));
// [{"id":1,"name":"Ada"}] — returned directly, no await anywhere

// Verified module surface, no npm install required:
// $ node -e "console.log(Object.keys(require('node:sqlite')))"
// [ 'DatabaseSync', 'StatementSync', 'Session', 'constants', 'backup' ]

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.