Setting NODE_ENV to "production" without --minify

I want to use the replaceNodeEnv flag together with treeshake to be able to create separate build outputs for production and development. To insert additional checks and console.logs only if the library user is in development. But the env field seems to not be able to overwrite the default "development" for non-minified builds. I don’t want to use --minify, so that the output code is easier to inspect. Is there any other way to set the NODE_ENV to "production", so that it’s respected by replaceNodeEnv?

[egoist]

Isn’t this the same as the env field in the tsup config file? I’ve tried it, but with no luck as well. I’ll make a repro if it’s something that is supposed to work already

yes please

[thetarnav]

I’ve stumbled on this issue recently again, but this time I was able to walk around it by defining esbuildOptions instead:

esbuildOptions(options) {
  options.define = {
    ...options.define,
    'process.env.NODE_ENV': '"production"',
  };
},

Here is the “fixed” example: https://stackblitz.com/edit/tsup-treeshake-development-issue-qobqkw