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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@the-forgebase/knex-libsql

v0.0.6

Published

A Knex dialect for using [LibSQL](https://libsql.org/) / [Turso](https://turso.tech/).

Readme

@the-forgebase/knex-libsql

A Knex dialect for using LibSQL / Turso.

This allows you to use the power of Knex.js query builder with LibSQL databases.

Installation

npm install knex @the-forgebase/knex-libsql libsql

or

pnpm add knex @the-forgebase/knex-libsql libsql

or

yarn add knex @the-forgebase/knex-libsql libsql

Usage

To use this dialect, you need to configure Knex to use @the-forgebase/knex-libsql as the client.

import { knex } from 'knex';
import { LibSqlKnexClient } from '@the-forgebase/knex-libsql';

const db = knex({
  client: LibSqlKnexClient,
  connection: {
    // For local file database
    filename: 'file:my.db', 
    
    // For remote database with Turso
    // url: process.env.TURSO_DATABASE_URL,
    // authToken: process.env.TURSO_AUTH_TOKEN,
  },
  useNullAsDefault: true,
});

// Now you can use `db` to build queries
async function example() {
  await db.schema.createTable('users', (table) => {
    table.increments('id');
    table.string('name');
  });

  await db('users').insert({ name: 'ForgeBase' });

  const users = await db('users').select('*');
  console.log(users);

  await db.destroy();
}

example();

The client property should be the LibSqlKnexClient class imported from this package. The connection object is passed to the LibSQL driver.

For local development, you can use a filename for a local SQLite file.

For remote databases, like Turso, you can provide a url and authToken.

Why @the-forgebase/knex-libsql?

The official knex-libsql package (@libsql/knex-libsql) is a great lightweight option. However, it is based on the sqlite3 package, whereas this package uses better-sqlite3.

This package takes a different approach by extending Knex's built-in better-sqlite3 dialect. This allows us to leverage the existing, mature, and feature-rich functionalities of the better-sqlite3 dialect while adapting it to work with libsql. This can provide a more stable and full-featured experience for developers already familiar with Knex's SQLite integrations.

Credits

This package is heavily based on the SQLite dialect implementation from MikroORM.

Specifically, the following files were adapted:

We are grateful for the excellent work done by the MikroORM team.