I’m using Prisma’s vscode extension but it’s showing error if I’m trying to use environment variable for

binaryTargets

. Does anyone knows how to fix this? ( I can still generate, migrate, etc. so I think it’s an extension issue..?)

Hey @Eddy Nguyen 👋 The reason for this is that the VSCode process doesn’t have the env var set. A way to work around this (although not a great one) is to start VSCode from the terminal where the env var is set.

Thanks @Ryan ! TIL I could set the env var on VScode from the terminal. So in this case, do you know why

env("PRISMA_DATABASE_URL")

works? I don’t think I have that set either 🤔

The reason is that we built special handling into the parser that is used by the VSCode extension that ignores those errors. But we implemented it only for the 

datasource.url

 property and not for the

binaryTarget

🙂

ah gotcha, thanks!