[eslint] eslint-plugin-lit

https://www.npmjs.com/package/eslint-plugin-lit is excellent, but we don’t include it in our config. Our config should work also when you’re not using lit, but since it’s our default recommendation I think we should offer this somehow.

How shall we do this? A separate package? I don’t think an eslint config can have multiple exports, right?

The create package would also need to update and include the correct linting configuration

[LarsDenBakker]

Now that I think about it, how bad is it to just include this plugin in the default config? Most of it’s users will use lit, and for those who don’t the plugin just won’t do anything. There are lots of linting options that won’t ever apply to many people.

Our linting doesn’t include that much special anyway, it’s easy for people to assemble their own.

The lit plugin isn’t lit-element specific either, so for example people using haunted will benefit from it as well.

Our other tools are lit-biased here and there as well.

[LarsDenBakker]

Can you disable specific linting rules per package? I think option 1 is ok for now, it’s a more specialist use case anyway.