Change to `process?.env?.NODE_ENV`?

In order to make the ESM builds work on modern browsers, without additional bundlers involved, would you consider change the way process.env.NODE_ENV is accessed to gracefully handle a missing process?

process?.env?.NODE_ENV or maybe process?.env.NODE_ENV should be enough.

[agilgur5]

Yea I’ll agree with @taion that the browser ESM use-case should use a production minified bundle (like I mentioned in https://github.com/jaredpalmer/tsdx/issues/631#issuecomment-602131471), which would have process.env.NODE_ENV replaced and then DCE’d. The browser ESM use-case is quite different from the Node/bundler use-case.

[taion]

Well, hold on a sec. I feel like I’m missing something here.

If you look at e.g., the point of something like https://github.com/4Catalyzer/babel-plugin-dev-expression#invariant is to result in better production code after going through a minifier that does dead code elimination.

If you’re distributing code as-is, then it seems like you wouldn’t want this.

It seems a little odd to run code that has gone through this transform in the browser without an additional DCE step, but I’m probably just missing something?