Closed wcandillon closed 8 years ago
Released 4.0.1, which fixes this issue.
The problem was with semver being pretty restrictive about prerelease tags: "If a version has a prerelease tag (for example, 1.2.3-alpha.3) then it will only be allowed to satisfy comparator sets if at least one comparator with the same [major, minor, patch] tuple also has a prerelease tag." - https://docs.npmjs.com/misc/semver
I fixed it by changing the tslint peerDependency to ^3 || >=3.1.0-dev
. Note that this also makes gulp-tslint incompatible with the future version of tslint 4.x, which is a good thing. Also note that 3.0.0-dev releases are not supported. If someone really wants that support I might accept a PR. The problem is that the list of supported dev releases starts to grow pretty quickly, and soon it would be something like this: ^3 || >=3.0.0-dev || >=3.1.0-dev || >=3.2.0-dev || >=3.3.0-dev || >=3.4.0-dev || >=3.5.0-dev
.
If someone knows a good way to specify those versions, drop me a line.
For comparison, here's grunt-tslint's solution: https://github.com/palantir/grunt-tslint/blob/master/package.json#L38
thanks a lot!
When using
tslint@next
, the peer dependency declaration conflicts: