`transform-remove-console` exclude options not working on React Native project

Describe the bug

I’m using the exclude options but it doesn’t seem to have any effect as all logs are removed.

To Reproduce

.babelrc

{
  "presets": ["react-native", "react-native-dotenv"],
  "env": {
    "production": {
        "plugins": [ ["transform-remove-console", { "exclude": [ "error", "warn", "info"] }] ]
    }
  }
}

Actual Output

All console.* output is removed.

Expected Output

console.warn, console.info and console.error should still work.

Configuration

How are you using babel-minify?

“metro-minify-uglify”

Additional context

React Native 0.54.4

[bareynol]

For anyone that happens upon this, and has been affected by it, I’ve found that using the following as my babel.config.js works properly to include transform-remove-console in production builds for react native projects, and properly uses the exclude property if specified:

module.exports = function(api) {
  api.cache(true);
  if (process.env.NODE_ENV === 'production' || process.env.BABEL_ENV === 'production') {
    return {
      "presets": ["module:metro-react-native-babel-preset"],
      "plugins": ["react-native-paper/babel", ["transform-remove-console", {"exclude": ["error", "warn", "info"]}]]
    }
  } else {
    return {
      "presets": ["module:metro-react-native-babel-preset"],
    }
  }
}

[bareynol]

I updated to react-native 0.61.2 and modified my babel.config.js to return a function with the signature function(api)

module.exports = function(api) {
  console.log("BABELCONFIG", api.version, api.env("production"), api.env(), process.env.NODE_ENV, process.env.BABEL_ENV);
  return {
    "presets": ["module:metro-react-native-babel-preset"],
    "plugins": ["react-native-paper/babel", "transform-remove-console"]
  }
}

During build I get the following output:

transform[stdout]: BABELCONFIG 7.6.2 true production production production
transform[stdout]: BABELCONFIG 7.6.2 true production production production
transform[stdout]: BABELCONFIG 7.6.2 true production production production
transform[stdout]: BABELCONFIG 7.6.2 true production production production
transform[stdout]: BABELCONFIG 7.6.2 false undefined production undefined
transform[stdout]: BABELCONFIG 7.6.2 false undefined production undefined
transform[stdout]: BABELCONFIG 7.6.2 false undefined production undefined
transform[stdout]: BABELCONFIG 7.6.2 true production production production
transform[stdout]: BABELCONFIG 7.6.2 true production production production
transform[stdout]: BABELCONFIG 7.6.2 false undefined production undefined
transform[stdout]: BABELCONFIG 7.6.2 false undefined production undefined
transform[stdout]: BABELCONFIG 7.6.2 false undefined production undefined

using plugins at top level allows the listed plugins to work, but using the env: {production: { plugins: [...]}} format does not work.

It appears as though BABEL_ENV is sometimes set to ‘production’ and sometimes undefined, and NODE_ENV is not being used when BABEL_ENV is undefined. I’m at a loss as to why