This repository has been archived by the owner on Dec 1, 2019. It is now read-only.
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 will prevent issues like #226 and #229 from being raised again
(hopefully).
awesome-typescript-loader
2.2.3 onwards brokecompatibility with TypeScript 2.0 and some people (including myself)
depended on it. Unfortunately, it failed silently, leaving a rather
cryptic error. TypeScript's dependency was updated as a devDependency on
this package to 2.0.2, however TypeScript itself has never been
installed as a peerDependency.
Adding TypeScript as a peerDependency will alert consumers of this
package when they install a version of TypeScript that is not supported
by this plugin.
Of course, perhaps
>= 2.0.2
is too weak a constraint, but it's betterthan none.
Here's what will be displayed if you install a version below the required version (in this example I installed TypeScript 2.0.0)