_unsupportedIterableToArray is broken

[umanghome]

Bug Report

• I would like to work on a fix!

Current Behavior
_unsupportedIterableToArray has a bug where if the iterable is of type Map or Set, it does Array.from on iterable.constructor.name instead of the iterable itself.

Broken Code

babel/packages/babel-helpers/src/helpers.js

Line 1047 in 1b777f5

if (n === "Map" || n === "Set") return Array.from(n);

This was introduced in #11268.

Expected behavior/code
Array.from should be called on o and not on n.

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

Environment

• Babel version(s): v7.9.0
• Node/npm version: v12.15.0
• OS: macOS 10.15.2
• Monorepo: no
• How you are using Babel: loader

Possible Solution
Replace

if (n === "Map" || n === "Set") return Array.from(n);

with

if (n === "Map" || n === "Set") return Array.from(o);

[babel-bot]

Hey @umanghome! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."

[nicolo-ribaudo]

Wow good catch! If you want to open a PR, we can release it in the next patch.

[umanghome]

@nicolo-ribaudo: My colleague @ChintanAcharya would be working on the fix. Can you assign this to him?

[nicolo-ribaudo]

Sure! But he has to leave a comment here first. Otherwise, GitHub doesn't show me his username in the assignees dropdown 😛

[ChintanAcharya]

Hey @nicolo-ribaudo! I'll be picking this up.

[umanghome]

@nicolo-ribaudo When will this be released?

[nicolo-ribaudo]

I'll release later today.