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

umzug-libsql

v0.0.1

Published

Umzug implementation with LibSQL Client

Downloads

3

Readme

umzug-libsql

Umzug implementation with LibSQL Client.

This package also exposes a CLI with sensible defaults for managing database migrations.

Running via CLI

Configuration reference

| Environment Variable | Config Property | Default | Description | |----------------------|-----------------|---------|-------------| | TURSO_DATABASE_URL | url | :memory: | The database URL for LibSQL | | TURSO_AUTH_TOKEN | authToken | undefined | Authentication token for the database | | UMZUG_GLOB | glob | db/migrations/*.sql | Glob pattern for migration files | | UMZUG_CONFIRM_BEFORE_DOWN | confirmBeforeDown | true | Whether to be asked for confirmation before running down migrations. With you're running multiple down migrations in a single command, it will execute all down migrations after confirmation |

Run CLI using npx

npx umzug-libsql --help

By default, db url will be set to :memory:, you can customize it via environment variables

for example:

TURSO_DATABASE_URL=http://localhost:8080/ npx umzug-libsql

or you can specify path to your env file

npx --env .env umzug-libsql

Run via custom file

you can also customize the config in a file

cli.js

import { createLibSqlUmzug } from './db/umzug.js';
const { umzug } = createLibSqlUmzug({
  url: ':memory:',
  authToken: '...',
  glob: 'db/migrations/*.sql',
  confirmBeforeDown: true
});
umzug.runAsCLI();
node cli.js

Use it from javascript code

Instead of running migrations from cli, you can also run it from javascript code. This is very useful for running migrations during tests.

For example in the code blow, you will get a fresh database with all tables but no data for each function

import { createLibSqlUmzug } from "umzug-libsql";

const umzug = createLibSqlUmzug();

beforeEach(async () => {
  await umzug.down({
    to: 0,
  });
  await umzug.up();
});

Custom umzug instance

If you want to create your own umzug instance you can do it like this:


import { Umzug } from "umzug";
import { createClient } from '@libsql/client';
import { LibSqlStorage, createLibSqlResolver } from "umzug-libsql";

const client = createClient();

const storage = new LibSqlStorage(client);
const resolver = createLibSqlResolver(client, { confirmBeforeDown: false });

const umzug = new Umzug({
  migrations: {
    glob: "migrations/*.sql",
    resolve: resolver,
  },
  storage,
  logger: console,
});

await umzug.up();