IMO minor versions can add warnings but not errors.

In my experience it's not that uncommon for your code to not build with a bump in TypeScript version as it finds some new type bugs in your code. I'm assuming that when you bump the version of TypeScript in this library then my code won't be able to be linted?

That said, I'm not sure if we need to do a major bump even if technically this is a breaking change (TypeScript doesn't). I think it makes the number bigger than it needs to be.

@aboyton, we are not installing typescript and we are allowing to use*, but we are only testing against one version and if yours is not same as defined in package you are going to see warning in console.

https://github.com/typescript-eslint/typescript-eslint#supported-typescript-version

@aboyton, we are not installing typescript and we are allowing to use*, but we are only testing against one version and if yours is not same as defined in package you are going to see warning in console.

https://github.com/typescript-eslint/typescript-eslint#supported-typescript-version

Sounds great. Ignore me then. Personally I try to keep on the tip as much as I can and so as long as you do too I don't really mind how you name things. Thanks everyone again for all of the work on this. Now to bump to 3.2 to I can start using this :)

It would be nice to be able to silence the warning with an environment variable or something to that effect, though. Runningeslint in parallel on a monorepo prints a big warning banner for every single package that is checked; same if you have multiple instances ofeslint-loader (one warning for each instance, you'll likely have at least 3 instances if usingthread-loader).

If no change, can we support both versions? For example,

-     "typescript": "~3.2.1"+     "typescript": ">=3.2.1 <3.4.0"

From memory there’s a way to turn the warning off. Can we document that as I’ve had to do it in the past as I had tools that required ESLint to output nothing when nothing was wrong? In the past I’ve wanted to update TypeScript versions faster than this repo has (and so silenced the warning).

I have implemented all the feedback.

• There is now a supported range of >=3.2.1 <3.4.0
• Better docs
• New documentedwarnOnUnsupportedTypeScriptVersion parserOption forparser which istrue by default to match the current behaviour

Codecov Report

Merging#184 intomaster willincrease coverage by<.01%.
The diff coverage is100%.

@@            Coverage Diff            @@##           master    #184      +/-   ##=========================================+ Coverage    96.2%   96.2%   +<.01%=========================================  Files          51      51                Lines        2449    2451       +2       Branches      368     369       +1     =========================================+ Hits         2356    2358       +2  Misses         48      48                Partials       45      45