Issue 1:
Bug Report

I would like to work on a fix!

i would but laziness you know

Current behavior

In the newly released Webpack 5 (released 3 days ago as of writing this), for a lot of files that are required by webpack to work, you get the following error example:

ERROR in ../node_modules/@babel/runtime/helpers/esm/toConsumableArray.js 4:0-52
Module not found: Error: Can't resolve './nonIterableSpread' in 'D:\projects\unfinished\app\a-guide\node_modules\@babel\runtime\helpers\esm'
Did you mean 'nonIterableSpread.js'?
BREAKING CHANGE: The request './nonIterableSpread' failed to resolve only because it was resolved as fully specified
(probably because the origin is a '*.mjs' file or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
@ ../node_modules/rc-table/es/Table.js 3:0-78 212:24-42 214:34-52
@ ../node_modules/antd/es/table/Table.js 9:0-51 405:19-33
@ ../node_modules/antd/es/table/index.js 1:0-28 2:15-20
@ ../node_modules/antd/es/index.js 56:0-43 56:0-43
@ dll library

REPL, Codesandbox, or GitHub Repo helps!

Input Code

No code is written, this occurs even in the most basic-est of webpack configurations (however mostly occurs in dlls)

Expected behavior

The files should be compiled into webpack successfully

Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)

Filename: babel.config.js

there is none

Environment

Babel version(s): [e.g. v6.0.0, v7.0.0-beta.34] webpack's one

Node/npm version: [e.g. Node 8/npm 5] node 12.18.4/6.14.6 & 14.13.0/6.14.8

OS: [e.g. OSX 10.13.4, Windows 10] windows 10

Monorepo: [e.g. yes/no/Lerna] - dont know what that is so presumed not

How you are using Babel: [e.g. cli, register, loader] through webpack

Possible Solution

just add file extensions in your imports

Additional context

webpack broke a lot of files lmao

Issue 2:
Bug Report

Current Behavior

A clear and concise description of the behavior.

When using Babel with useBuiltIns: "usage" and corejs: 3 I am getting the error "Const must be initialized error" in IE 11. There is a for loop that uses const and I believe that is the cause here; it is not being transpiled correctly.

Note: browserlist

"browserslist": "> 0.25%, not dead, ie >= 11",

When I set debug in .babelrc I get the following:

@babel/preset-env: `DEBUG` option

Using targets:
{
"android": "4.4.3",
"chrome": "49",
"edge": "17",
"firefox": "64",
"ie": "11",
"ios": "8",
"opera": "57",
"safari": "11.1",
"samsung": "4"
}

Using modules transform: auto

Using plugins:
transform-template-literals { "android":"4.4.3", "ie":"11", "ios":"8", "safari":"11.1" }
transform-literals { "android":"4.4.3", "ie":"11", "ios":"8" }
transform-function-name { "android":"4.4.3", "chrome":"49", "edge":"17", "ie":"11", "ios":"8", "samsung":"4" }
transform-arrow-functions { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-block-scoped-functions { "android":"4.4.3", "ios":"8" }
transform-classes { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-object-super { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-shorthand-properties { "android":"4.4.3", "ie":"11", "ios":"8" }
transform-duplicate-keys { "android":"4.4.3", "ie":"11", "ios":"8" }
transform-computed-properties { "android":"4.4.3", "ie":"11" }
transform-for-of { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }
transform-sticky-regex { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-dotall-regex { "android":"4.4.3", "chrome":"49", "edge":"17", "firefox":"64", "ie":"11", "ios":"8", "samsung":"4" }
transform-unicode-regex { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "safari":"11.1", "samsung":"4" }
transform-spread { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-parameters { "android":"4.4.3", "edge":"17", "ie":"11", "ios":"8", "samsung":"4" }
transform-destructuring { "android":"4.4.3", "chrome":"49", "edge":"17", "ie":"11", "ios":"8", "samsung":"4" }
transform-block-scoping { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-typeof-symbol { "android":"4.4.3", "ie":"11", "ios":"8" }
transform-new-target { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
transform-regenerator { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }
transform-exponentiation-operator { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }
transform-async-to-generator { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }
proposal-async-generator-functions { "android":"4.4.3", "chrome":"49", "edge":"17", "ie":"11", "ios":"8", "safari":"11.1", "samsung":"4" }
proposal-object-rest-spread { "android":"4.4.3", "chrome":"49", "edge":"17", "ie":"11", "ios":"8", "samsung":"4" }
proposal-unicode-property-regex { "android":"4.4.3", "chrome":"49", "edge":"17", "firefox":"64", "ie":"11", "ios":"8", "samsung":"4" }
proposal-json-strings { "android":"4.4.3", "chrome":"49", "edge":"17", "ie":"11", "ios":"8", "safari":"11.1", "samsung":"4" }
proposal-optional-catch-binding { "android":"4.4.3", "chrome":"49", "edge":"17", "ie":"11", "ios":"8", "samsung":"4" }
transform-named-capturing-groups-regex { "android":"4.4.3", "chrome":"49", "edge":"17", "firefox":"64", "ie":"11", "ios":"8", "samsung":"4" }

Using polyfills with `usage` option:

[/Users/blakewilson/server/public/vidbg/src/vidbg.js] Added following core-js polyfills:
es.symbol { "android":"4.4.3", "ie":"11", "ios":"8", "samsung":"4" }
es.array.concat { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }
es.array.filter { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }
es.array.for-each { "ios":"8" }
es.object.define-property { "ios":"8" }
es.object.get-own-property-descriptor { "android":"4.4.3", "ie":"11", "ios":"8" }
es.object.keys { "android":"4.4.3", "ie":"11", "ios":"8" }
web.dom-collections.for-each { "android":"4.4.3", "chrome":"49", "ie":"11", "ios":"8", "samsung":"4" }

I noticed that every plugin has a browser target of IE 11 set except for transform-block-scoped-functions. You can see the browser targets are only { "android":"4.4.3", "ios":"8" }

Input Code

REPL or Repo link if applicable:

You can view the repo here:

https://github.com/blakewilson/vidbg/tree/v2

Expected behavior/code

A clear and concise description of what you expected to happen (or code).

The expected behavior is that Babel would correctly transpile block scoping for IE 11.

Babel Configuration (.babelrc, package.json, cli command)

{
"presets": [
[
"@babel/preset-env",
{
"debug": true,
"useBuiltIns": "usage",
"corejs": 3,
}
]
],
"plugins": ["@babel/plugin-proposal-class-properties"]
}

Environment

Babel version 7.4.0

node 11.9.0 npm 6.5.0

MacOS Mojave 10.14.3

Babel Loader / Webpack

Possible Solution

Additional context/Screenshots

Add any other context about the problem here. If applicable, add screenshots to help explain.

Viewing the repo linked above should give a good idea of what is going on.

Any context would be very appreciated! I have been stuck on this for quite a while.