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

netlify-plugin-prisma-provider

v0.3.0

Published

Swap out the schema.prisma provider dynamically at build time

Downloads

141

Readme

netlify-plugin-prisma-provider

Currently, if you're using Prisma to talk to your database, there is no way to set the database provider dynamically. The url connection string can be set via ENV var, but not the provider:

// schema.prisma

datasource DS {
  provider = "sqlite"
  url      = env("DATABASE_URL")
}

If you want to use a SQLite database locally, but use Postgres in production, there is no way to swap out the provider "sqlite" for "postgresql" once you go to production—the string for the provider must be present in this file before Prisma generates the client libraries.

Prisma has an open issue for letting you set this value via ENV var but there is no planned release date.

Until then, this plugin will swap out the provider for you right before your code is built on Netlify. You can set your preferred production database provider as an environment variable and it will be swapped into schema.prisma right before the build begins.

NOTE: The plugin will only replace the provider if its value is sqlite. If postgresql or mysql is present then the replacement is skipped. If switching between Postgres and MySQL in development and production is needed, open an issue and I'll update the plugin to support this scenario!

As of Prisma's beta3 release their migration scripts look at the provider in each migration's snapshot of schema.prisma and compare those against the url in the main schema.prisma. If the protocol doesn't match the provider it will raise an error during the migration. Starting in version 0.3.0 of this plugin, we will also replace the provider in each of the migration snapshots' copy of schema.prisma and steps.json.

Usage

Add a [[plugins]] entry to your netlify.toml file:

[[plugins]]
package = 'netlify-plugin-prisma-provider'
  [plugins.inputs]
  path = 'prisma/schema.prisma'
  varName = 'DATABASE_PROVIDER'

| name | description | default | |------|-------------|---------| | path | The path to the schema.prisma file, relative to the root of your codebase. | prisma/schema.prisma | | varName | The name of the ENV variable that contains the provider name. | DATABASE_PROVIDER |

Add the environment variable in Netlify with the name you provided varName and a value of postgresql or mysql:

image

If you don't set the environment variable it will assume you want to use postgresql and will replace that in your schema.prisma. If you don't want that to happen then you'll need to remove this plugin completely!