<p dir="auto">As far as I can tell the <code class="notranslate">runtime</code> transform is all-or-nothing, all I'm interested in is getting rid of the redundant helpers inlined into every module, but it seems I can't have that without also the "risk" of getting dependencies on the other runtimes (notably <code class="notranslate">core-js</code>).</p>
<p dir="auto">Have I missed something or would it not make sense to have a separate transform for just this? They seem to have rather separate concerns from my perspective (avoid redundant helper code vs add dependencies for optional features).</p>
<p dir="auto">This would be really nice for larger applications that aren't libraries, where they could still use the full, globally polluting polyfill, but the helpers wouldn't be duplicated across several modules. It would make the compiled code faster to load, and a lot smaller overall. These benefits are nice for both Node applications and web applications, where the deduplication would make programs significantly smaller. As for the core-js aliasing, it could just require the module at the top of every file that needs a feature from it, which doesn't add a lot of size overhead to the files.</p>