<h2 dir="auto">Bug Report</h2>
<p dir="auto">Webpack5 <code class="notranslate">beta.30</code> has enabled strict mode on the ESM modules imports <a href="https://github.com/webpack/webpack/releases/tag/v5.0.0-beta.30">https://github.com/webpack/webpack/releases/tag/v5.0.0-beta.30</a></p>
<p dir="auto"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="700423058" data-permission-text="Title is private" data-url="https://github.com/webpack/webpack/issues/11467" data-hovercard-type="issue" data-hovercard-url="/webpack/webpack/issues/11467/hovercard" href="https://github.com/webpack/webpack/issues/11467">webpack/webpack#11467</a> has noted people with code problems, however <code class="notranslate">@babel/runtime</code> appears to have code that doesn't follow the strict <code class="notranslate">"type": "module"</code> requirements, as expected for node / webpack.</p>
<p dir="auto"><code class="notranslate">.\node_modules\@babel\runtime\helpers\esm\package.json</code> has <code class="notranslate">"type": "module"</code> being set and libraries that depend on <code class="notranslate">@babel/runtime</code> with ESM modules are broken as a result.</p>
<p dir="auto">I expect the code generator should be outputting with the file extensions to satisfy the requirements of ESM modules</p>
<p dir="auto"><a href="https://nodejs.org/api/esm.html#esm_differences_between_es_modules_and_commonjs" rel="nofollow">https://nodejs.org/api/esm.html#esm_differences_between_es_modules_and_commonjs</a></p>
<p dir="auto"><strong>Current behavior</strong></p>
<p dir="auto">@babel/runtime/helpers/esm/*.js contains extensionless imports for dependencies.</p>
<p dir="auto"><strong>Expected behavior</strong></p>
<p dir="auto">@babel/runtime/helpers/esm/*.js to contain fully specified extensions for imports</p>
<p dir="auto"><strong>Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)</strong></p>
<p dir="auto">N/A - this is npm published module</p>
<p dir="auto"><strong>Environment</strong></p>

<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 12.18.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.8 - C:\s\SwiftFox\node_modules\.bin\npm.CMD
  Monorepos:
    Yarn Workspaces: 1.22.5
  npmPackages:
    @babel/core: 7.11.4 =&gt; 7.11.4
    babel-loader: 8.1.0 =&gt; 8.1.0
    eslint: 7.7.0 =&gt; 7.7.0
    webpack: 5.0.0-beta.30 =&gt; 5.0.0-beta.30"><pre class="notranslate"><code class="notranslate">  System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 12.18.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.8 - C:\s\SwiftFox\node_modules\.bin\npm.CMD
  Monorepos:
    Yarn Workspaces: 1.22.5
  npmPackages:
    @babel/core: 7.11.4 =&gt; 7.11.4
    babel-loader: 8.1.0 =&gt; 8.1.0
    eslint: 7.7.0 =&gt; 7.7.0
    webpack: 5.0.0-beta.30 =&gt; 5.0.0-beta.30
</code></pre></div>
<p dir="auto">Since the script depends on babel-core, it starts to require <code class="notranslate">babel-runtime/core-js/*</code> files which are created by the script.</p>