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 🙏

© 2024 – Pkg Stats / Ryan Hefner

sqlite-opfs

v0.0.4

Published

Sqlite wasm build using the origin private file system

Downloads

10

Readme

This is a wrapper around @sqlite.org/sqlite-wasm that uses the origin private file system. It also handles running the sqlite code in a web worker while providing a nice API to query on.

There are two requirements for this library to work:

  • You'll need to provide a web worker factory for the sqlite wrapper to use. The library can't handle this since it's bundler specific and node_modules imports are not able to create web workers with relative imports without some configuration on the bundler side.
  • You need to ensure that your server includes specific headers for Atomics and SharedArrayBuffer to work properly. See https://sqlite.org/wasm/doc/trunk/persistence.md#coop-coep for more information.

You may need to use something like https://github.com/gzuidhof/coi-serviceworker if you can't control the headers on the server.

Installation

npm i sqlite-opfs @sqlite.org/sqlite-wasm

Note that @sqlite.org/sqlite-wasm is a peer dependency which is why it's not included in the installation command.

Vite users will also have to add optimizeDeps this to their vite config:

export default defineConfig({
	optimizeDeps: {
		exclude: ['@sqlite.org/sqlite-wasm'],
	},
	// ...
});

Usage

import init from 'sqlite-opfs';

// For vite usage
import SqliteWorker from 'sqlite-opfs/worker?worker';

const sqlite = await init({
	getWorker: () => new SqliteWorker(),
});
const db = await sqlite.open('myDb');
// await db`DROP TABLE IF EXISTS myTable`.run();
await db`CREATE TABLE IF NOT EXISTS myTable (id INTEGER PRIMARY KEY, name TEXT)`.run();
await db`INSERT INTO myTable (name) VALUES ('Alice')`.run();
await db`INSERT INTO myTable (name) VALUES ('Alan')`.run();
await db`INSERT INTO myTable (name) VALUES ('Billy')`.run();
await db`INSERT INTO myTable (name) VALUES ('Bob')`.run();
await db`INSERT INTO myTable (name) VALUES ('Brian')`.run();

console.log(
	'changes',
	await db`UPDATE myTable SET name = name || '!' WHERE name LIKE 'B%'`.run(),
);

console.log('all', await db`SELECT * FROM myTable`.all());
console.log('just name', await db`SELECT * FROM myTable`.all('name'));
console.log('one', await db`SELECT * FROM myTable`.one());

const like = 'B%';
console.log(
	'escape',
	await db`SELECT * FROM myTable WHERE name LIKE ${like}`.all(),
);

for await (const row of db`SELECT * FROM myTable`) {
	console.log('row', row);
}

// Can even run parallel queries
await Promise.all([
	(async () => {
		for await (const row of db`SELECT * FROM myTable`) {
			console.log('q1', row);
			await new Promise((r) => setTimeout(r, Math.random() * 100));
		}
	})(),
	(async () => {
		for await (const row of db`SELECT * FROM myTable`) {
			console.log('q2', row);
			await new Promise((r) => setTimeout(r, Math.random() * 100));
		}
	})(),
]);

Note the one() and all() methods also take a selector for the format of the result.

console.log('one', await db`SELECT * FROM myTable`.one('id', 'name')); // logs { id: SqlValue, name: SqlValue }
console.log('one', await db`SELECT * FROM myTable`.one(['id', 'name'])); // logs SqlValue[]
console.log('one', await db`SELECT * FROM myTable`.one([])); // logs all as SqlValue[]
console.log('one', await db`SELECT * FROM myTable`.one()); // logs all as Record<string, SqlValue>
console.log('one', await db`SELECT * FROM myTable`.one({})); // logs all as Record<string, SqlValue>

You can also wrap the worker in a worker of your own to have code that lives within the same context of the worker. For example:

// my-worker.ts
import { addHook } from 'sqlite-opfs/worker';

addHook({
	onOpen: async (db) => {
		db.createFunction(
			'add_numbers',
			(_ctx, ...args) => {
				let sum = 0;

				for (const arg of args) {
					sum += Number(arg);
				}

				return sum;
			},
			// Needed for variadic functions, otherwise use the `callback.length` value.
			{ arity: -1 },
		);
	},
});
import SqliteWorker from './my-worker?worker';

const sqlite = await loadSqliteWrapper({
	getWorker: () => new SqliteWorker(),
});
const db = await sqlite.open('myDb');
console.log(await db`SELECT 1, 2, add_nums(10, 20, 30)`.one([])); // logs [1, 2, 60]