npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

sql.js-as-sqlite3

v0.2.3

Published

sqlite3-compatible interface for sql.js

Readme

sql.js-as-sqlite3

A wrapper around sql.js (a web-browser version of SQLite) that exposes the same API interface as sqlite3 connected to a normal SQLite database.

Demo

Why?

sequelize is an ORM that supports many databases, including SQLite, which is written in C++. Specifically, sequelize uses sqlite3 package to "talk" to SQLite. Both SQLite and sqlite3 package were written in C++ and weren't originally designed to work in a web browser.

Then appeared an unofficial port of SQLite to WASM (web-browser-compatible code) called sql.js. Because sqlite3 is not designed to work in a web browser, it won't support this sql.js web-browser-compatible port. And because sequelize relies exclusively on sqlite3 when working with SQLite, it won't support sql.js either.

But there's a loophole in sequelize — specifically, a dialectModule parameter — that allows swapping the sqlite3 module with any arbitrary one so long as it keeps the same "interface".

So the workaround is to create a wrapper around sql.js so that for sequelize it becomes indistinguishable from sqlite3, effectively tricking sequelize into thinking that it still works with SQLite over sqlite3 in Node.js instead of actually working with sql.js in a web browser.

And this is all that sql.js-as-sqlite3 package does.

Install

npm install sql.js sql.js-as-sqlite3 --save

If you're not using a "bundler" then use a standalone version from a CDN.

Use

Node.js

import sqlite3 from 'sql.js-as-sqlite3'

// Use it as if it was `sqlite3`
const db = new sqlite3.Database(':memory:')

Browser (with bundler)

import sqlJsAsSqlite3 from 'sql.js-as-sqlite3'
import initSqlJs from 'sql.js'

sqlJsAsSqlite3.configure({
  // `sql.js` package default export.
  initSqlJs,
  // Base URL for `sql.js` to get the `*.wasm` files like `sql-wasm-debug.wasm`.
  // The version of the `*.wasm` files must match the version of the `sql.js` package.
  // Must end with a "/".
  wasmFileBaseUrl: 'https://cdnjs.cloudflare.com/ajax/libs/sql.js/1.10.2/'
})

// Use it as if it was `sqlite3`
const db = new sqlite3.Database(':memory:')

Browser (no bundler)

When not using a "bundler", one can import the package in a web browser by including it from a CDN such as unpkg.com or jsdelivr.com

<script src="https://unpkg.com/[email protected]/bundle/sql.js-as-sqlite3.min.js"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/sql.js/1.10.2/sql-wasm.min.js"></script>
<script>
  // Base URL for `sql.js` to get the `*.wasm` files like `sql-wasm-debug.wasm`.
  // The version of the `*.wasm` files must match the version of `sql.js`.
  // Must end with a "/".
  SQL_JS_WASM_FILE_BASE_URL = 'https://cdnjs.cloudflare.com/ajax/libs/sql.js/1.10.2/'
</script>

<script>
  // Use it as if it was `sqlite3`
  const db = new sqlJsAsSqlite3.Database(':memory:')
</script>

Sequelize

This package could be used to make sequelize ORM work with sql.js (a port of SQLite database that works in a web browser):

import Sequelize from 'sequelize'
import sqlite3 from 'sql.js-as-sqlite3'

const sequelize = new Sequelize('sqlite://:memory:', {
  dialectModule: sqlite3
})

For a server-side example, see a test.

For a client-side example, see sequelize-browser package.

Notes

In April 2023, SQLite released an official WASM-compatible npm package intended to be used in a web browser. It could be viewed as an "official" alternative to sql.js which was itself released in late 2016 and is still maintained as of early 2026. Which one is "better" for web-browser use? I personally don't really bother to care. I guess sql.js author could come up with a benchmark or a readme comparison section.

References

Based on the code by @domasx2.

GitHub

On March 9th, 2020, GitHub, Inc. silently banned my account (erasing all my repos, issues and comments, even in my employer's private repos) without any notice or explanation. Because of that, all source codes had to be promptly moved to GitLab. The GitHub repo is now only used as a backup (you can star the repo there too), and the primary repo is now the GitLab one. Issues can be reported in any repo.

License

MIT