From a53192d19fb4c1289d1e25958709d6a08426e171 Mon Sep 17 00:00:00 2001
From: Mike Hartington <mikehartington@gmail.com>
Date: Mon, 20 Oct 2025 14:56:44 -0400
Subject: [PATCH] doc(prisma-config): update example using environment
 variables

---
 .../325-prisma-config-reference.mdx           | 23 ++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/content/200-orm/500-reference/325-prisma-config-reference.mdx b/content/200-orm/500-reference/325-prisma-config-reference.mdx
index 73d50374ad..0c8ec29c23 100644
--- a/content/200-orm/500-reference/325-prisma-config-reference.mdx
+++ b/content/200-orm/500-reference/325-prisma-config-reference.mdx
@@ -356,7 +356,28 @@ export default {} satisfies PrismaConfig;
 
 ### Using environment variables
 
-When using `prisma.config.ts`, environment variables from `.env` files are not automatically loaded. You'll need to:
+When using `prisma.config.ts`, environment variables from `.env` files are not automatically loaded. If you're using node or deno, you'll need to: 
+
+1. Pass a `--env-file` flag to the command line 
+
+<TabbedContent code>
+<TabItem value="Node">
+```terminal
+node --env-file=.env index.js
+node --env-file=.env --env-file=.local.env index.js
+```
+</TabItem>
+<TabItem value="Deno">
+```terminal
+deno run --env-file main.ts
+deno run --env-file=.env --env-file=.local.env main.ts
+```
+</TabItem>
+</TabbedContent>
+
+For Bun, `.env` files are automatically loaded.
+
+For releases of Node before v20, you'll need to: 
 
 1. Install the `dotenv` package: