Node module specific rules about eslint-plugin-unicorn

[jamestalmage]

It all comes back to type analysis. The easier it is to infer that a given variable is of a given type, the easier it is to write this type of rule.

[sindresorhus]

@jamestalmage Sure, but in this case, the template literal or string is always put inline in the function call. If not, we could always use path analysis it's a 99% certainty it's in the same file. But yeah, many other cases might be harder. I don't think that should limit our brainstorming here though.

[jamestalmage]

Oh - I meant ensuring meow was meow. But yes, it also applies to the template variable as well. Not against it - just saying adding a lot of type dependent rules without a good typing system is burdensome (echoing what we have already said)

[sindresorhus]

@jamestalmage Yeah, totally, but don't limit your brainstorming to type dependent rules. Lots of other things that could be useful. I should have found a better example in the issue description than a type dependent one.

[jamestalmage]

My point was that type analysis is required for any "uses XXX appropriately" rule. You have to narrow down that a given variable is of type XXX. It's easy for meow since you basically always use the import directly.

[fregante]

Closing discussion as inactive for 4 years. Now there's a node-specific plugin: https://github.com/mysticatea/eslint-plugin-node