Remove noEmit option from tsconfig.json in TypeScript project skeleton #11136
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
Remove the `noEmit` option due to conflicts with the `incremental` option.
|
|
chris-tse
changed the title
|
Should note that this combination will be allowed with TypeScript 4.0 which is in beta now. https://devblogs.microsoft.com/typescript/announcing-typescript-4-0-beta/#noemit-and-incremental |
|
Oh that's good to know. I'll leave this here in case the team wants to add it in before the 4.0 release. Otherwise, feel free to close the issue and PR! |
|
There’s already a PR for updating TypeScript: meteor/babel#33. |
|
lets close it because the next version of meteor-babel will contain TS 4+ |
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.
Addresses #11135
Remove the
noEmitoption due to conflicts with theincrementaloption.