SQLocal makes it easy to run SQLite3 in the browser, backed by the origin private file system.
SQLocal makes it easy to run SQLite3 in the browser, backed by the origin private file system.
SQLocal makes it easy to run SQLite3 in the browser, backed by the origin private file system. It wraps the WebAssembly build of SQLite3 and gives you a simple interface to interact with databases running on device.
Documentation - GitHub - NPM - Fund
…
Log:
[
{ id: 1, name: 'bread' },
{ id: 2, name: 'milk' },
{ id: 3, name: 'rice' }
]
Or, you can use SQLocal as a driver for Kysely or Drizzle ORM to make fully-typed queries.
import { SQLocalKysely } from 'sqlocal/kysely';
import { Kysely, Generated } from 'kysely';
// Initialize SQLocalKysely and pass the dialect to Kysely
const { dialect } = new SQLocalKysely('database.sqlite3');
const db = new Kysely({ dialect });
// Define your schema
// (passed to the Kysely generic above)
type DB = {
groceries: {
id: Generated;
name: string;
};
};
// Make type-safe queries
const data = await db
.selectFrom('groceries')
.select('name')
.orderBy('name', 'asc')
.execute();
console.log(data);
See the Kysely documentation for getting started.
…
See the Drizzle ORM documentation for declaring your schema and making queries.
Install the SQLocal package in your application using your package manager.
npm install sqlocal
# or...
yarn add sqlocal
# or...
pnpm install sqlocal
In order to persist data to the origin private file system, this package relies on APIs that require cross-origin isolation, so the page you use this package on must be served with the following HTTP headers. Otherwise, the browser will block access to the origin private file system.
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
How this is configured will depend on what web server or hosting service your application uses. If your development server uses Vite, see the configuration below.
Vite needs some additional configuration to handle web worker files correctly. If you or your framework uses Vite as your build tool, you can use SQLocal's Vite plugin to set this up.
The plugin will also enable cross-origin isolation (required for origin private file system persistence) for the Vite development server by default. Just don't forget to also configure your production web server to use the same HTTP headers.
Import the plugin from sqlocal/vite and add it to your Vite configuration.
import { defineConfig } from 'vite';
import sqlocal from 'sqlocal/vite';
export default defineConfig({
plugins: [sqlocal()],
});
No open issues yet, or sync has not completed.