With AVA we're applying our own preset to enable stage-4 syntax features on various Node.js versions. The way users opt-out of this behavior is by disabling the preset.
I'm looking to build AVA's Babel pipeline on the low-level APIs exposed by @babel/core. Unfortunately (though understandably) loadPartialConfig() removes disabled plugins / presets, so I can't tell if the user intended to disable it.
I realize in our case I could look at the AVA-specific test options and resolve the preset, but it'd be nice if it could be disabled anywhere in the user's Babel configuration chain.
Might there be a way for loadPartialConfig() to preserve disabled plugins / presets?
With AVA we're applying our own preset to enable stage-4 syntax features on various Node.js versions. The way users opt-out of this behavior is by disabling the preset.
I'm looking to build AVA's Babel pipeline on the low-level APIs exposed by
@babel/core. Unfortunately (though understandably)loadPartialConfig()removes disabled plugins / presets, so I can't tell if the user intended to disable it.I realize in our case I could look at the AVA-specific test options and resolve the preset, but it'd be nice if it could be disabled anywhere in the user's Babel configuration chain.
Might there be a way for
loadPartialConfig()to preserve disabled plugins / presets?