babel-plugin-transform-remove-console is not run for production where it matters

[Crare]

looking at the example it says:

npm install babel-plugin-transform-remove-console --save-dev

Which means it will be saved to devdependencies. It will not be run in production is NODE_ENV is set to production. I think the installation example is little bit bad because of this. If you set NODE_ENV=production it will not install and run devDependencies at all.

I think the installation instructions should be changed to:

npm install babel-plugin-transform-remove-console

Please do correct me if I'm wrong.
Or is this not meant for production use? Maybe state that then.

[nicolo-ribaudo]

During development/deployment, you will compile and minify your code. Then, during production, your code will already be minified, so you will not need to run the Babel plugin anymore.

[Crare]

I would guess so for the web.
But what if it is used for Mobile apps like React Native or React Native with Expo, will it work the same?

I noticed also that Expo is not recommending to use the NODE_ENV variable, which is true as it seems to break the building-phase if 'production' is used as value for it. It gives error of some packages in devDependencies not found. This might be more of a Expo problem then.
Anyway I fixed it by changing the way environments are handled in the expo project...