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?
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too