Ed S

Note that we have fixed this issue our maintained fork: https://github.com/wikimedia/eslint-plugin-no-jquery/blob/master/rules/utils.js#L32

Wouldn't that then just be a very specific version of `no-unused-vars`, which is in eslint:recommend?

I think #475 is preferable. Even on my fast device the large readme takes >2000ms to load, and on my mobile device it often hangs. Having an index + individual...

These three files total

I would recommend using i18n files rather than maintaining parallel branches. You could use a plugin such as https://kazupon.github.io/vue-i18n/, then keep all the messages in separate files `i18n/en.json`, `i18n/fr.json` etc.

As an open source project you would even be able to get your translations done for free by the [TranslateWiki community](https://translatewiki.net/wiki/Translating:New_project/en). This is the same site that does translations for...

I think this is problematic when the recommended replacement is not available in your target version, for example `url.parse` is deprecated as of Node11 in favour of `new url.URL` (introduced...

Sure, but given we know the Node version and we know when each API was introduced, why not make feature of this? I think that would be more useful that...

Could be an option instead?

There's no reason to use ID's at all, they're evil.