-
Notifications
You must be signed in to change notification settings - Fork 945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decouple core.js results from Babel an TypeScript #1333
Comments
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 |
Even better!
…On Thu, Aug 2, 2018 at 11:13 AM, Sergey Rubanov ***@***.***> 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
<#1333 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABRIeEc2MhBzHlziwzMq6XXrvP9YfofTks5uMwkNgaJpZM4VsWpi>
.
|
Even better! |
I'd also like to see three columns - one for babel without core-js, and one for with v2, and one for with v3. |
That would make the number of columns explode over time, since the BabelXcore.js and TypeScriptXcore.js combinations would increase exponentially. |
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. |
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. |
One big problem: a serious part of |
Indeed, and that's information people need to know. |
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?
The text was updated successfully, but these errors were encountered: