Environment variable not found

Bug description

Since version 2.24.0 I got next error while making requests to my graphql server

"Error: Context creation failed: ",
"Invalid `prisma.user.findUnique()` invocation:",
"  error: Environment variable not found: DATABASE_URL.",
"  -->  schema.prisma:3",
"   | ",
" 2 |   provider = \"postgresql\"",
" 3 |   url      = env(\"DATABASE_URL\")",
"   | ",

Commands like prisma migrate works correctly

I have next file structure

├── prisma
│   └── schema.prisma
├── src
│   └── server.ts
├── .env

In version 2.23.0 everything works as expected

How to reproduce

1. Create graphql-server with apollo-server and prisma
2. Add PrismaClient to context
3. Make graphql request

Expected behavior

No response

Prisma information

My schema.prisma file starts like this

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["orderByRelation", "selectRelationCount"]
}

Environment & setup

• OS: Windows
• Database: PostgreSQL
• Node.js: 14.15.4
• apollo-server-express: 2.25.1

Prisma Version

2.24.0

[oceandrama]

@janpio Yes, I use Yarn Workspaces in my project

[ljosberinn]

I’m seeing the same issue beginning with version 2.24.0. In my case, it’s due to different behaviour leading up to /sdk/utils/tryLoadEnvs.

v2.23.0:

config value being passed to getPrismaClient:

Notice the schemaEnvPath being 'C:\\Users\\gerr.it\\Desktop\\dev\\keystone-heroes\\packages\\@keystone-heroes\\db\\.env' and debug statements being present.

v2.24.0

config value being passed to getPrismaClient:

Notice the line difference which in the code screenshot indicating the changes between the versions, although this function wasnt touched and how schemaEnvPath now is 'C:\\Users\\gerr.it\\Desktop\\dev\\keystone-heroes\\node_modules\\.prisma\\client\\packages\\@keystone-heroes\\db\\.env'.

It’s late right now, I’ll try to whip up a repro tomorrow.

Edit: updated the config values. Apparently despite the name, config.relativeEnvPaths are no longer relative in 2.24.0.