fix NODE_ENV interpolation in vite production build

[maxsbelt]

I received an error in my project:

I'm using vitejs toolchain and seems like it replaces process.env.NODE_ENV string with true/false value during the build, but it doesn't replace process.env['NODE_ENV'] (see source).

I got the problem because in my particular case one of the modules are declares process variable (so it's not an undefined) but vitejs doesn't specify process.env.

I'm suggesting to replace current check with process.env.NODE_ENV === 'production'. In this case vitejs can easily replace this string with particular value during the build.

This is should be safe update because there are plenty of popular packages that do the same check:

• react
• redux
• react-query
• emotion

If you will search for process.env.NODE_ENV in node_modules you will see plenty of search results:

But process.env['NODE_ENV'] only appears in react-dnd: