Closed OliverJAsh closed 6 years ago
Tbh I just copied eslint/eslint - I am not sure of the reason behind it.
It was probably a mistake to do that, if you donβt mind submitting a PR to loosen it again, Iβll get it merged.
We did it on the ESLint side to try to allow as many features as possible in the codebase-- sometimes a new feature on 10.x might get backported to a late version in 9.x. So we tried to minimize the chance of compatibility issues by using later version of the non-LTS branches.
@platinumazure Interesting, thanks.
@JamesHenry Do you want to stick with that, or can I raise a PR to lower the range? I'm using 9.8.0β¦
It's a tricky one - Is there a specific reason why you are using 9.8 and not 9.10? I imagine not, you just aren't.
So you could easily upgrade node, but on the other hand it's just another point of friction to using the lib, so avoiding it might be best...
I'm going to loosen it again
Would it be possible to release this?
occurred error as same issue.
typescript-eslint-parser@16.0.0: The engine "node" is incompatible with this module. Expected version "^6.14.0 || ^8.10.0 || >=9.10.0".
my node version: v8.9.4
Sorry for the delay, @OliverJAsh @Jungwoo-An, 16.0.1 is out now
@JoaquinAraujo The error you're seeing is for the eslint package, not typescript-eslint-parser. ESLint has not loosened their compatibility, but typescript-eslint-parser has.
Is this intentional?