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

vitest-environment-prisma

v0.4.2

Published

Vitest testing environment for prisma migrate and teardown scripts

Downloads

90

Readme

vitest-environment-prisma

Vitest testing module for prisma migrate and teardown scripts. See ⚡️ Vitest Environment for more details.

Actions

Setup

Environment runs prisma migrate deploy in your application to bootstrap test database.

:warning: Be aware that this can update your production database if you are not carefull. Use this only on development and always check your .env credentials

Teardown

Environment will drop your test database depending on your adapter


Adapters

Databases supported by now:

  • mysql
  • psql
  • sqlite

Setup Environment

Example:

vite.config.ts

import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    environment: 'prisma', // Required
    environmentOptions: {
      adapter: 'mysql',
      envFile: '.env.test',
      prismaEnvVarName: 'DATABASE_URL', // Optional
      transformMode: 'ssr', // Optional
    }
  }
})

Environment Options

| Name | Description | Default | |:-----------------|:---------------------------------------------------------------|:---------------| | adapter | Name database adapter. See Adapters | mysql | | envFile | Name of the .env file for test suite | .env.test | | multiSchema | Option to support multiple prisma schemas | false | | schemaPrefix | Prefix to attach on the database name | | | prismaEnvVarName | The environment variable used for the Prisma DB connection URL | DATABASE_URL | | transformMode | This value determines how plugins will transform source code | ssr |

Database Credentials

The following keys must be present on your .env.test file:

| Name | Description | Example | |:----------------|:----------------------------------|:-------------------------| | DATABASE_USER | Database user credential | root | | DATABASE_PASS | Database user password credential | root | | DATABASE_HOST | Database connection host | localhost, 127.0.0.1 | | DATABASE_PORT | Database connection port | 5432, 3306 | | DATABASE_NAME | Database name | mydb |

These credentials are necessary to construct the DATABASE_URL env value (can be overridden, see above) to which the prisma connection will be made. See the Prisma database connections for more information on how to properly set the connection URL from an environment variable.

Sqlite config

If you are using the sqlite adapter only the DATABASE_NAME env is required. The database file will be written to the /tmp directory.

Make sure to use only the name:

  • DATABASE_NAME=mydb :heavy_check_mark:
  • DATABASE_NAME=mydb.db :heavy_check_mark:
  • DATABASE_NAME=file:/mydb :heavy_multiplication_x:
  • DATABASE_NAME=../mydb :heavy_multiplication_x: