This repository was archived by the owner on Oct 2, 2021. It is now read-only.
Use actual TypeScript instead of @babel/preset-typescript.#25
Merged
Use actual TypeScript instead of @babel/preset-typescript.#25
Conversation
Babel's TypeScript implementation has a few unfortunate caveats: https://babeljs.io/docs/en/babel-plugin-transform-typescript#caveats Most notably, the lack of *full* support for namespaces is painful: babel/babel#8244 babel/babel#9785 By precompiling TypeScript code with the actual TypeScript compiler, we can support features like namespaces without relying on Babel. Of course, Babel still handles everything after TypeScript syntax has been removed.
benjamn
commented
Jul 6, 2019
| @@ -1,4 +1,7 @@ | |||
| const enum TestResult { PASS, FAIL } | |||
Contributor
Author
There was a problem hiding this comment.
This verifies that the const enum caveat no longer applies.
benjamn
pushed a commit
to meteor/meteor
that referenced
this pull request
Jul 6, 2019
TypeScript is now supported by the actual TypeScript compiler, rather than by @babel/preset-typescript: meteor/babel#25
5 tasks
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Babel's TypeScript implementation has a few unfortunate caveats: https://babeljs.io/docs/en/babel-plugin-transform-typescript#caveats
Most notably, the lack of full support for namespaces is painful:
By precompiling TypeScript code with the actual TypeScript compiler, we can support features like namespaces without relying on Babel. Of course, Babel still handles everything after TypeScript syntax has been removed.