Create account

DEV Community

Uncaught ReferenceError: process is not defined

Fred B. on August 20, 2023

How to solve the following error ? Uncaught ReferenceError: process is not defined First, this happens when, in ...

Read full post

Amanda Branwell • Nov 2 '23

You, sir, are a lifesaver! (Also created an account just to say that.)

SOONG-E • Oct 11 '23 • Edited

you are a genius

Alvaro • Oct 30 '23

i'd created this account just to tell you: u r my f*cking hero

shanganegoda • Feb 10 '24

Seems like "process.env" is removed, have to use "import.meta.env" instead.
So instead of process.env.VITE_SOME_KEY -> import.meta.env.VITE_SOME_KEY

Read more here - vitejs.dev/guide/env-and-mode.html

tim.rohrer • Mar 21 '24

I suspect this is the actual solution, but I can't say as I understand why VITE deviates from the standard approach.

AgustinGonzalezDev • Mar 13 '24

Graciass geniooooooooooooooooooooooooo!!!

Mukwaba John Baptist (Media-vybz) • Jun 24 '24

on my side, loadEnv was throwing an error then i revised my code s below. things worked perfectly. thanks for the clue i was totally lost

import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
import dotenv from 'dotenv';

dotenv.config(); // Load environment variables from .env

// vitejs.dev/config/
export default defineConfig(({ mode }) => {
return {
define: {
'process.env.REACT_APP_BASE_URL': JSON.stringify(process.env.REACT_APP_BASE_URL),
},
plugins: [react()],
};
});

Frank Garcia • Nov 18 '24 • Edited

Just do it the Vite way and forget all of this!

Add your .env files e.g. ".env.testing".
Use "VITE_" as the prefix for the variables instead of "REACT_APP_" e.g. "VITE_SOME_NAME".
Use "import.meta.env" instead of "process.env" e.g. "import.meta.env.VITE_SOME_NAME".

Done.