To be honest, I'm not sure how to handle it.

It's basically the same issue as #1283 and it will emerge every time standard needs to be used with newer technologies. Unfortunately, those techs are popping up too often and developers are forced to adapt to them quickly. However, standard can't and that makes it hard to sell standard to stakeholders.

Options:

For such cases use standardx — though, it's a deviation from standard vision. Kinda makes standard itself not that useful.
Incorporate any required changes right into the standard — that will bloat lib with not essential features. Besides, as shows experience with TypeScript — it takes wayyy to long, to the point where people start to use other linters just because they can't use it with important tech right now.
Allow to add and override rules — unfortunately, it's a deviation from standard vision too.
Provide the way to extend or override rules with standard plugins — they'd be a bridge between eslint rules and standard. However, in fact, it's the same as 3, but only masked.

Still impossible to use Vue plugin #1282

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions