can confirm the workaround works.

moving .env from root folder into .react-email

I investigated a bit and I think I understand why this happens.
Since react-email package is the one that runs the app, the process.env reads from the .react-email directory, hence why your workaround works.
I've also logged the directory with process.cwd() and I can confirm that is indeed what happens, even logging it through the files inside the emails folder.

I've been trying to wrap my head around on how to fix this issue, and there's an easy solution which is to use the dotenv library and then use the .config to set the path to the parent folder, which is hacky and non intuitive.

The other option is to think of a way for the react-email package to point to the .env of the parent, somehow.

Let me know what would be best and I can get to work on a PR to fix this issue.

Not sure who your reply is addressed to, but I don't have a preference at this point since I'm now running a script before running locally in order to set up some ngrok stuff and my workaround is simply baked into that script. But I imagine any solution where the root environment variable files would just work would suffice.

It's not a "workaround" it's just a hack for email dev, what about email export? It doesn't create .react-email folder.

Created a patch to solve the problem for both dev and export (for 1.9.5):

diff --git a/node_modules/react-email/dist/source/commands/dev.js b/node_modules/react-email/dist/source/commands/dev.js
index c0f050a..6e63dd9 100644
--- a/node_modules/react-email/dist/source/commands/dev.js
+++ b/node_modules/react-email/dist/source/commands/dev.js
@@ -8,16 +8,20 @@ const utils_1 = require("../utils");
 const fs_1 = __importDefault(require("fs"));
 const shelljs_1 = __importDefault(require("shelljs"));
 const run_server_1 = require("../utils/run-server");
+const _env = require("dotenv").config();
+const _env_file = Object.entries(_env.parsed).map(([k, v]) => `${k}="${v}"`).join("\n") + "\n";
 const dev = async ({ dir, port, skipInstall }) => {
     try {
         if (!fs_1.default.existsSync(dir)) {
             throw new Error(`Missing ${dir} folder`);
         }
         if (fs_1.default.existsSync(utils_1.REACT_EMAIL_ROOT)) {
+            fs_1.default.writeFileSync(utils_1.REACT_EMAIL_ROOT + "/.env", _env_file);
             await (0, run_server_1.setupServer)('dev', dir, port, skipInstall);
             return;
         }
         await (0, utils_1.downloadClient)();
+        fs_1.default.writeFileSync(utils_1.REACT_EMAIL_ROOT + "/.env", _env_file);
         await (0, run_server_1.setupServer)('dev', dir, port, skipInstall);
     }
     catch (error) {
diff --git a/node_modules/react-email/dist/source/commands/export.js b/node_modules/react-email/dist/source/commands/export.js
index e3b8200..5e99456 100644
--- a/node_modules/react-email/dist/source/commands/export.js
+++ b/node_modules/react-email/dist/source/commands/export.js
@@ -39,6 +39,8 @@ const path_1 = __importDefault(require("path"));
 const shelljs_1 = __importDefault(require("shelljs"));
 const fs_2 = __importDefault(require("fs"));
 const close_ora_on_sigint_1 = require("../utils/close-ora-on-sigint");
+const _process_env = {};
+require('dotenv').config({ processEnv: _process_env });
 /*
   This first builds all the templates using esbuild and then puts the output in the `.js`
   files. Then these `.js` files are imported dynamically and rendered to `.html` files
@@ -48,12 +50,17 @@ const exportTemplates = async (outDir, srcDir, options) => {
     const spinner = (0, ora_1.default)('Preparing files...\n').start();
     (0, close_ora_on_sigint_1.closeOraOnSIGNIT)(spinner);
     const allTemplates = glob_1.glob.sync((0, normalize_path_1.default)(path_1.default.join(srcDir, '*.{tsx,jsx}')));
+    const define = {};
+    for (const k in _process_env) {
+        define[`process.env.${k}`] = JSON.stringify(_process_env[k]);
+    }
     esbuild_1.default.buildSync({
         bundle: true,
         entryPoints: allTemplates,
         platform: 'node',
         write: true,
         outdir: outDir,
+        define,
     });
     spinner.succeed();
     const allBuiltTemplates = glob_1.glob.sync((0, normalize_path_1.default)(`${outDir}/*.js

Place the patch into patches/react-email+1.9.5.patch in your project.
Make sure that dotenv package is installed.
Apply the patch using the marvelous patch-package npm module.

Would also love this to be fixed 🙏 I'm using React Email in a project when I've set up T3 Env and I can't even start the dev server due to the missing env variables:

❌ Invalid environment variables: {
  ...
}

Would also love this to be fixed 🙏 I'm using React Email in a project when I've set up T3 Env and I can't even start the dev server due to the missing env variables:

❌ Invalid environment variables: {
  ...
}

Is this from using t3-env within the /emails files?

Just use process.env in those files and follow this to copy the .env file to the generated react-email previewer:
#668 (comment)

Copying the environment variables to ./node_modules/react-email/ doesn't seem to work with "react-email": "3.0.1". Any idea on how to handle it now?

it seems to work if you copy the .env file to ./node_modules/react-email/dist/preview/. I wonder if there's a better way to do it.

How can we access environment variables for "email export"?

How can we access environment variables for "email export"?

Terminal:
TEST_ENV_VAR=asdef email export

In tsx template:
console.log(process.env.TEST_ENV_VAR);

asdef

Works fine

For Windows users, the solution with cp doesn't work since it's not a recognized command. Use the Windows copy command instead:
"email:dev": "copy .env.local .\\node_modules\\react-email\\dist\\preview\\ && email dev -p 3001 --dir src/components/emails"
Make sure to use backslashes for paths and note that I'm copying from .env.local (which is my Next.js environment file) to the React Email preview directory.
Thanks to everyone in this thread, especially @LavransBjerkestrand and @viczam 🫶

How can we access environment variables for "email export"?

Terminal: TEST_ENV_VAR=asdef email export

In tsx template: console.log(process.env.TEST_ENV_VAR);

asdef

Works fine

would be cool if you could show how it works for u. for me it just works for the preview but not for the "email export" script. it stays undefined

"import "dotenv/config"; "

inside of my ParentComponent of each template. so it must be imported one by one for each template.

might be a special case for me and doesnt work for u since im using it inside of a node service.

Hello everyone 👋,

I'm looking for feedback on this issue: #{2074} (process.env not recognized in React Email). If you have any ideas or time to help, please let me know!

Thanks in advance 🙏.

you did not understand github. Dont open a second issue with exactly the same issue. Specially not with "i solved it" its not an issue if you solved it.

Here's what worked for me :

🔧 What I did

1. I installed dotenv:

npm install dotenv

2. I set the environment variable in the .env file

// .env
NEXT_PUBLIC_VERCEL_ENV=development

3. In test.tsx file, I used dotenv/config to load the environment variables

import "dotenv/config";

import { Html } from '@react-email/html'
import { Text } from '@react-email/text'
import { Section } from '@react-email/section'
import * as React from 'react'

const publicVercelEnv = `${process.env.NEXT_PUBLIC_VERCEL_ENV}`

export default function Email() {
    return (
        <Html>
            <Section style={{ backgroundColor: '#ffffff', margin: '0 auto' }}>
                <Text>
                    {publicVercelEnv}
                </Text>
            </Section>
        </Html>
    )
}

Here's what worked for me :

🔧 What I did

1. I installed dotenv:

npm install dotenv

2. I set the environment variable in the .env file

// .env
NEXT_PUBLIC_VERCEL_ENV=development

3. In test.tsx file, I used dotenv/config to load the environment variables

import "dotenv/config";

import { Html } from '@react-email/html'
import { Text } from '@react-email/text'
import { Section } from '@react-email/section'
import * as React from 'react'

const publicVercelEnv = ${process.env.NEXT_PUBLIC_VERCEL_ENV}

export default function Email() {
return (

<Section style={{ backgroundColor: '#ffffff', margin: '0 auto' }}>

{publicVercelEnv}



)
}

this is not optimal. you have to do it for each email individually.

Here's what worked for me :

🔧 What I did

1. I installed dotenv:

npm install dotenv

2. I set the environment variable in the .env file

// .env
NEXT_PUBLIC_VERCEL_ENV=development

3. In test.tsx file, I used dotenv/config to load the environment variables

import "dotenv/config";
import { Html } from '@react-email/html'
import { Text } from '@react-email/text'
import { Section } from '@react-email/section'
import * as React from 'react'
const publicVercelEnv = ${process.env.NEXT_PUBLIC_VERCEL_ENV}
export default function Email() {
return (

{publicVercelEnv}

)
}

this is not optimal. you have to do it for each email individually.

were only users ourself, those are workarounds. A workaround is never optimal. Use dotenv in the Parent of each template, that is the current workaround until someone with knowledge of the project fixes it.

Converting this to a discussion, since this isn't a bug, it's more of a feature request. Let's keep this discussion to the level of thinking of an API for users to load their env files in, which is a completely valid use case.