Regression in loading .env file from 2.2.0 to 2.2.2 for prisma/cli

Bug description

When upgrading from @prisma/cli from 2.2.0 to 2.2.2 it does not load the .env file from the working directory, like the prisma client does. We already had prisma-client at 2.2.2 because dependabot merged that PR first.

Fun fact: if you put the DATABASE_URL from the .env file back in the prisma/.env file, the client doesn’t work any more (because it doesn’t have the DATABASE_URL) but npx prisma migrate up works again 🤷 .

How to reproduce

Breaking CLI:

1. Upgrade CLI and Client to 2.2.2
2. Place a .env file with the DATABASE_URL in the working directory, and none in prisma/.
3. run regular prisma code -> it works
4. run npx migrate up --experimental -> it breaks

Breaking the normal client:

1. Upgrace CLI and Client to 2.2.2
2. Create a prisma/.env file with the DATABASE_URL and no .env file in the working directory.
3. run regular prisma code -> it breaks (using the default empty constructor new PrismaClient())
4. run npx migrate up --experimental -> it works again

Environment & setup

• OS: Mac OS
• Database: Postgres
• Prisma version: 2.2.2
• Node.js version: 14.4

Related to #2971

[janpio]

In Setup 2, Prisma Client should totally work if you have env("DATABASE_URL") in your schema.

If not, can you create a super simple project reproducing the problem and just put it on GitHub so we can verify?

[alexnederlof]

Sorry guys haven’t found the time to isolate the issue in a fresh repo. I’ll try to do it in the coming weeks, but feel free to close the issue and have me re-open it if I can confirm, if that helps you manage this repo better!