Environment variables loaded from uses wrong directory separator (slashes) on Windows

[janpio]

C:\Users\Jan\Documents\throwaway\1313>prisma introspect
Environment variables loaded from ./prisma/.env

Introspecting based on datasource defined in prisma\schema.prisma …
Error: P1001

[jonahsnider]

Here's a line that's assuming the path separator is /:

prisma/src/packages/cli/src/bin.ts

Line 80 in 0118def

dotenvResult = dotenv.config({ path: 'prisma/.env' })

When working with paths in Node you should always use path.join to avoid quirks like this:

import { join as joinPaths } from 'path';

dotenv.config({ path: joinPaths('prisma', '.env') });

[timsuchanek]

Thanks @pizzafox but that line is not the problem.
The Dotenv library under the hood uses the path library and therefore can deal with the /.
The problem is just the hardcoded / path separator.

Using a simple path.relative solves this problem.

[timsuchanek]

Thanks a lot for reporting 🙏
This issue is fixed in the latest dev version of @prisma/cli.
You can try it out with npm i -g @prisma/cli@dev.

In case it’s not fixed for you - please let us know and we’ll reopen this issue!