I'm not sure this is necessary, since it's only a migration from the perspective of official Vue lib maintainers. For those using this in their projects, it serves the same purpose and should support all the features it did previously, plus many more. Does that make sense?

Hmm, technically yes. But we don't know yet if it will have all the settings it had previously. From what I understood this plugin was made for internal projects purposes thus it's in my opinion too opinionated and we should reevaluate all settings and make sure it's as generic as can be. It had only one rule so we'll probably leave it, but other settings - we'll see. If we'll leave any they'll for sure will be added in recommended configuration and not the base one. I'm on it.

On the other hand users don't necessarily need to know what's going on with eslint-plugin-vue-libs as it has been made only for internal purposes and the one that they should be interested in is this one. And we'll probably publish v3.0.0 after integratin eslint-plugin-vue-trail anyway, so fine. Makes sense @chrisvfritz 👍