fix: only augment vue, not sub-packages

[BobbieGoede]

Based on your description of type issues in nuxt-modules/i18n#2629 (comment) I took a quick look.

There's a weird type augmentation behavior when modules mix augmenting vue and @vue/runtime-core resulting in broken types (see nuxt/nuxt#28542). This may not be the fix for the plugin type definitions, I wasn't able to run npm scripts to test it myself, probably due to some local package manager issues.

[s00d]

Yes, thank you, these are the remnants of my experiments with typing. I’ll try to remove them and see what happens

[azhirov]

@BobbieGoede Thank you for pointing that out, but the issue you mentioned regarding type augmentation when mixing vue and @vue/runtime-core is actually related to how the IDE (like WebStorm / PHPStorm) resolves types within .vue files. The problem isn't with the type definitions themselves but with how the IDE prioritizes @vue/runtime-core over the augmented vue module. If the types are correctly extended in the vue module, there shouldn't be any conflict or need for additional fixes in the plugin definitions.
However, if we don't extend the @vue/runtime-core type, the IDE fails to recognize types like $localeRoute, $t, $tc, and others.

[danielroe]

I believe it is TypeScript behaviour, not just the IDE. See https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbzgYygUwIYzQQTGOAXzgDMoIQ4ByANwFc0qAoJ5CAOwGd4N84BeFOiy58ACgSEAlCwD0suAAEYnALRoAHmDTIY6qOShwARhiOcAFhDoAbACYm0cGAE9tDjJ2owoDZmy54AH0MAC44djoQYzQjQV4wADoAkmAAc0S0mwhTGwAFcm1YYDRORNMoOQVlNU1tXX1DUggIOEtre0dnNzQPLyofP1YObjgg43DI6NiBOATkjlSMrJyMfMLYmBKykhaWOx0bMycQCDtbJ1o-RCY4OGB2bCgSDGQnAGEKSHY0R-e6bgUAoQIpbUo3O53XYQcKDNC3IhMQj7Q7HOCnc42S6KehoWS+R6gNCqNjoKgQ+6PWIvN5wT7gDi-GD-QEgYGg7YUu4VWG+eF3ZGEIA for example.