Stop supporting node 10? about eslint-find-rules HOT 4 CLOSED

Small plug for using https://www.npmjs.com/package/safe-publish-latest to avoid accidental latest publishes when maintaining multiple version lines :-p

from eslint-find-rules.

You're correct that in order to support both eslint 2 and 3, you'll have to conditionally install eslint 2 for node < 4 in travis, and eslint 3 for node >= 4.

Personally I think this is worth it to maintain back compat for awhile - if you disagree, then surely you'll want to drop support for pre-node-4. However, eslint 3 kept support for the eslint 2 rule format precisely to give eslint 2 users time to upgrade - and the longer eslint-find-rules supports both, the easier it will be for eslint 2 users to smoothly upgrade to eslint 3.

from eslint-find-rules.

I'd definitely vote for keeping backwards compatibility for a while.
As I'd like to get the coloured output feature #52 also for ESLint 2 (in case it won't take us forever to realize it 😜 ), how about another dist-channel to enable certain features and fixes for ESLint 2 users, while generally proceeding with version 2 (for ESLint 3)?
(I personally have zero experience in using the npm dist channels though ...)

from eslint-find-rules.

Sounds good!

from eslint-find-rules.