Remove non-standard Babel's plugins #90
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Typescript only supports standard plugins? |
|
Typescript support stage3+ proposals |
|
They don't have plugins, features are being implemented in compiler itself, that's why they pick only standard features |
|
Ah, makes sense! Do you foresee that as a future problem? Where typescript lags behind such plugins? I dont know enough about the dev cycles of typescript :) |
|
About feature support — it neven was an issue to me (for more than two years). Frankly, I don't care about proposal (as the two I'm deleting), but when it comes to rather important features as spead/async/await/generators the lag isn't a problem, they release every two months |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to migrate to TypeScript, we have to get rid of non-standard language features
#89