What would be the best way to get .env variables into both NodeJS and Vite?

[MarByteBeep]

I'm writing shared code that runs on a server as a NodeJS application (e.g., node app.js) and on a SolidJS server that uses Vite. Both server and NodeJS application use sensitive variables that I would like to store in an .env file. I mean, that's where these things are for, right?

Vite uses import.meta.env to access environment variables prefixed with VITE_. The NodeJS application can use dotenv, however that will put those environment variables in process.env.

Ideally I'd like to write code without having to think about whether I run as a NodeJS app, or a Vite server app. I'm okay with prefixing all variables with VITE_ for the NodeJS application as well. However I don't know how to properly switch between process.env and import.meta.env.

Currently I came up with this work-around:

const env = import.meta?.env ? import.meta.env : process.env;
const mySensitiveVariable = VITE_VARIABLE;

Now my NodeJS application will start with import 'dotenv/config'; and the Vite server application will work out of the box. This works, but I don't particularly like that assumption on import.meta?.env being undefined in NodeJS applications, nor do I like to have to declare that

const env = import.meta?.env ? import.meta.env : process.env;

line each and everytime I use shared environment variables.

Anyone with a better idea?

[DaniilIsupov]

I also have such problems
I often encounter following problem

TypeError: Cannot read properties of undefined (reading 'SSR')

when I try to write the following code

if (import.meta.env.SSR) {

}

[mqklin]

@MarByteBeep have you found a solution?