Decouple core.js results from Babel an TypeScript

[afmenez]

The test results for Babel and TypeScript say "+ core.js 2.5", shouldn't it be upgraded to 3.0, which supports many new js features?

[chicoxyzzy]

IMO it's better to decouple core.js results from Babel and TypeScript and have two new columns core.js 2 and core.js 3

[afmenez]

Even better!

On Thu, Aug 2, 2018 at 11:13 AM, Sergey Rubanov notifications@github.com wrote:

IMO it's better to decouple core.js results from Babel an TypeScript and have two new columns core,js 2 and core.js 3

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kangax/compat-table/issues/1333#issuecomment-409940825, or mute the thread https://github.com/notifications/unsubscribe-auth/ABRIeEc2MhBzHlziwzMq6XXrvP9YfofTks5uMwkNgaJpZM4VsWpi .

[afmenez]

Even better!

[ljharb]

I'd also like to see three columns - one for babel without core-js, and one for with v2, and one for with v3.

[afmenez]

That would make the number of columns explode over time, since the BabelXcore.js and TypeScriptXcore.js combinations would increase exponentially.

[ljharb]

I'm not sure how "nothing, 1, 2" is any less explody than "1, 2" - with 1000 versions, we're talking about 1000 columns vs 1001 with my suggestion.

[afmenez]

Sorry, I thought you meant you wanted columns for every combination of BabelXcore.js and TypeScriptXcore.js. Now I see that you mean pure core.js, Babel and TypeScript for old versions, and combined for the latest. It's a lot of columns, anyway. :)

[zloirock]

One big problem: a serious part of babel features does not work without polyfills.

[ljharb]

Indeed, and that's information people need to know.