import { defineConfig } from 'vite'
// ...
export default defineConfig({
  // ...
  define: {
    'process.env': {}
  Holajuwon, xiaoxin-sky, Hammster, jacksteamdev, snowdream, zxbodya, mcmillenb, timmaier, natalie-o-perret, bitcoinvsalts, and 15 more reacted with thumbs up emoji
  mecirmartin, Lord-Y, and marcmec reacted with rocket emoji
      All reactions
          
Is there any way to support process.env way to access dotenv?

The problem is that using import.meta goes in conflict with jest (we use typescript):

kulshekhar/ts-jest#1174

And there's no viable way of using it for us without introducing babel and additional overhead.
The only other strategy is to give up on using Vite and roll back to vue cli, which is something that we are trying to avoid since we like Vite performances.
Is there any other way to set process.env?
I found that I can use the following in vite.config.ts to avoid "Uncaught ReferenceError: process is not defined":
import { defineConfig } from 'vite'
// ...
export default defineConfig({
  // ...
  define: {
    'process.env': {}
I personally do:
export default defineConfig({
  // ...
  define: {
    'process.env': process.env
I found that I can use the following in vite.config.ts to avoid "Uncaught ReferenceError: process is not defined":
import { defineConfig } from 'vite'
// ...
export default defineConfig({
  // ...
  define: {
    'process.env': {}
I personally do:
export default defineConfig({
  // ...
  define: {
    'process.env': process.env
This works for me while development but after build process becomes undefined.
          
All of these issues relating to undefined globals appear closed with no real resolutions. Is there some way of polyfilling these things (process, global, etc.) that actually works? I've tried rollup plugins like rollup-plugin-polyfill-node but im still facing issues.
Obviously the real culprit here is libraries which are behind the curve in supporting esm properly, but sometimes we need to use them.
Is there any way to support process.env way to access dotenv?

The problem is that using import.meta goes in conflict with jest (we use typescript):

kulshekhar/ts-jest#1174

And there's no viable way of using it for us without introducing babel and additional overhead.
The only other strategy is to give up on using Vite and roll back to vue cli, which is something that we are trying to avoid since we like Vite performances.
Is there any other way to set process.env?
Have you found any solution to this? Having the exact same issue at the moment.