Simon Renoult

Oh wow. Thanks for your contribution. It looks promising, I'll look into it :+1:

Hi @scottamplitude, I love the idea. Two things we should consider: 1. We loose the ability to evaluate other languages than JS/TS. While imperfect, `node-sloc` allowed `code-complexity` to support lots...

Hi, All good, thanks :+1: , I hope you are good as well. I think we can forget externalizing the strategies for now, it's not the priority. My others remarks...

I took the liberty to fork your PR in order to implement my own feedbacks: #30 It's quite close to being done. I just need to add a few unit...

Seems fair. I changed the wording a bit and merged it, thanks :+1:

Candidates: - https://www.npmjs.com/package/escomplex - https://eslint.org/docs/rules/complexity and its source https://github.com/eslint/eslint/blob/master/lib/rules/complexity.js

The issue still exists with `[email protected]`. Any update?

@henriklippke the PR has been merged, the feature is available in 4.3 :)

I just merged an alternative version using `escomplex`. Available in 4.3 :)

In the end, we'll keep node-sloc for simplicity sake and fallback to a manual line count when node-sloc does not support the file type.