Change to TypeScript@next #252
Closed
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
mohsen1
reviewed
Jun 13, 2018
|
@mohsen1 fair point, I have changed it to pin it to a specific the latest daily version. |
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.
This PR is more advisory. Once you get to dealing with throwing errors in TypeScript, you will encounter a bug in TypeScript 2.9.1 (and in theory 2.9.3 when it is released) that will throw an exception (See: microsoft/TypeScript#24638).
This is now fixed in master and the daily builds of TypeScript, but hasn't been back ported. Therefore migrating to
typescript@nextwill utilise the daily builds of TypeScript and avoid the issue.