Cloudflare Workers with PlanetScale db

I want to use prisma with Cloudflare workers and PlanetScale db using JS and not TS.

I have created the webpack config

module.exports = {
  entry: './src/index.js',
  target: 'webworker',
  resolve: {
    extensions: ['.ts', '.tsx', '.js', '.jsx'],
    // Alias for resolving the Prisma Client properly
    alias: {
      '@prisma/client$': require.resolve('@prisma/client'),
    },
  },
  devtool: 'none',
}

and schema

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["referentialIntegrity", "dataProxy"]
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
  referentialIntegrity = "prisma"
}

model Test {
  id            Int      @id @default(autoincrement())
  name          String
  city          String
  www           String

Now it all trows pleny of errors. When I try to use db push I get:

% npx prisma db push           
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Get config: Schema Parsing P1012

error: Error validating datasource `db`: the URL must start with the protocol `mysql://`.
  -->  schema.prisma:11
   | 
10 |   provider = "mysql"
11 |   url      = env("DATABASE_URL")
   | 

Validation Error Count: 1

Next while using wrangler dev I have a ton of lines mostly around missing modules.

What is more there is a missing step of using npx prisma db push.

[millsp]

Hey @konradbjk, hey everyone. We have released some changes a few minutes ago in prisma@3.15.0. tl;dr;

• Instead of PRISMA_CLIENT_ENGINE_TYPE, use prisma generate --data-proxy to enable the Data Proxy
• import { PrismaClient } from '@prisma/client/edge' for a Workers-compatible Prisma Client
• Please be aware that .env aren’t bundled into the generated Prisma Client any longer (see docs)
• You can also remove any package location aliasing from your build scripts
• Warnings around eval are now also fixed

Thanks everyone, and your feedback is welcome.

[SebJansen]

the URL must start with the protocol mysql://, I think it could be due to either of two reasons:

• Prisma client hasn’t been generated with dataproxy, do PRISMA_CLIENT_ENGINE_TYPE=dataproxy npx prisma generate. A mysql://... connection string only works for non-dataproxy projects, and Cloudflare Workers needs the dataproxy because Workers can only connect through HTTP which requires a connection string resembling prisma://....
• You have a space in your DATABASE_URL env var, it has happened often to me.