Global constant replacement doesn't work in production about vite HOT 3 CLOSED

you're not using it in your codebase and so it will be removed on build (tree shaked)

from vite.

@userquin thanks for the explanation! But this is still an issue since the app behaviour differs in dev and production modes.
Here's my case. A third-party dependency relies on a specific browser env variable and it was there during development. However, when deployed to production, the browser variable is no longer defined and the third-party code behaves differently. For me it was quite a challenge to figure out what was wrong. At least, this is something worth mentioning in the docs.

from vite.

I think this is working as expected too. The documentation already clarifies this:

Define global constant replacements. Entries will be defined as globals during dev and statically replaced during build.

from vite.