Why does a Babel preset‑env config that works locally fail in production builds?

The goal is to determine why a Babel configuration that compiles correctly in a local development environment produces incorrect or missing transforms when executed in a production build.

Key constraints involve potential differences in Babel version, browserlist target mappings, plugin ordering across combined presets, and the impact of minification on source map generation, none of which are explicitly documented for cross‑environment consistency.

Which Babel preset‑env target configuration is actually applied in production versus local development?
How does plugin ordering within combined presets affect the transforms when minification is enabled?