How do I migrate from version 1 to version 2 of Nessie?

Back up your data first, then update the config file to the new syntax, run the update_timestamps command to adjust file names and database entries, and refactor migration files to use class-based format as per the migration guide.

Can Nessie handle SQLite databases in Deno?

Yes, Nessie supports SQLite via the ClientSQLite client. You need to configure it in the nessie.config.ts file and ensure Deno has the necessary read/write permissions for the SQLite file.

Nessie vs Prisma for Deno: which should I choose?

Nessie is a dedicated migration tool with multi-database support and Deno-native design, but Prisma offers a broader ORM ecosystem and is now natively supported in Deno. If you need only migrations and prefer simplicity, Nessie works, but for full-featured ORM with ongoing maintenance, Prisma might be better.

How to create a custom migration template in Nessie?

Define a template file with your preferred code structure, then specify its path or URL in the nessie.config.ts using the migrationTemplate property, or pass it via the --migrationTemplate CLI flag when generating migrations.

What permissions does Nessie require in Deno?

Nessie needs --allow-read for config and migration files, --allow-write for creating files, --allow-net for database connections and remote imports, and --unstable for certain filesystem operations, as detailed in the permissions section.

Is Nessie compatible with TypeScript projects?

Yes, since Deno natively supports TypeScript, Nessie works out of the box with TypeScript migration and seed files, and the config file can be written in TypeScript as shown in examples.

How do I run Nessie migrations in a Docker container?

Use the provided Docker image from Docker Hub, mount your migration files and config, and run CLI commands inside the container, leveraging the image's pre-configured environment for seamless execution.

Open-Awesome

nessie

MITTypeScript2.0.11

A modular Deno library for PostgreSQL, MySQL, MariaDB, and SQLite database migrations.

GitHub

520 stars31 forks0 contributors

What is nessie?

Nessie is a database migration tool for Deno that helps developers manage schema changes and seed data across PostgreSQL, MySQL, MariaDB, and SQLite databases. It provides a CLI and programmatic API to version-control database structures, ensuring consistency across environments.

Target Audience

Deno developers building applications that require structured database schema management, particularly those working with PostgreSQL, MySQL, MariaDB, or SQLite.

Value Proposition

Developers choose Nessie for its Deno-native design, multi-database support, and modular CLI that simplifies migration workflows without external dependencies.

Overview

A modular Deno library for PostgreSQL, MySQL, MariaDB and SQLite migrations

Use Cases

Best For

Managing database schema changes in Deno applications
Version-controlling database migrations across PostgreSQL, MySQL, or SQLite
Seeding databases with test or initial data in development
Integrating migrations into CI/CD pipelines for Deno projects
Using Docker to containerize migration workflows
Creating custom migration templates for team-specific standards

Not Ideal For

Node.js projects or teams using non-Deno runtimes
Organizations requiring long-term, actively maintained tools for production
Applications needing migrations for databases like MongoDB, Oracle, or NoSQL systems
Environments where Deno's unstable permissions or flags are a security or operational concern

Pros & Cons

Pros

Deno-native design

Built specifically for Deno, it integrates seamlessly without external dependencies, leveraging Deno's module system and permissions as shown in the CLI usage examples.

Multi-database support

Provides dedicated clients for PostgreSQL, MySQL, MariaDB, and SQLite, allowing flexible database management across different systems.

Flexible CLI and templates

Offers a modular CLI with commands for migrations, rollbacks, and seeding, plus support for custom templates and remote file loading, enhancing workflow customization.

Docker integration

Includes a Docker image for containerized usage, making it easy to incorporate into CI/CD pipelines or isolated environments.

Cons

Impending unmaintenance

The README explicitly states the project will be unmaintained soon due to the author switching to Prisma, posing a risk for future updates and support.

Deno lock-in and ecosystem

Only works with Deno, limiting adoption in Node.js or mixed stacks, and relies on Deno's evolving ecosystem, which may have fewer third-party integrations.

Complex migration from version 1

Version 2 introduces breaking changes requiring manual migration steps, which can be error-prone and time-consuming for existing users.

Frequently Asked Questions

Related Projects

denodb

MySQL, SQLite, MariaDB, PostgreSQL and MongoDB ORM for Deno

Stars1,922

Forks128

Last commit2 years ago

postgres

PostgreSQL driver for Deno

Stars655

Forks97

Last commit1 year ago

deno_mongo

🍃 MongoDB driver for Deno 🦕

Stars512

Forks90