Failed to resolve component replacing blaze with static-html

[David-bfg]

I've run into this error with using static-html instead of blaze templates. Issue does not happen with blaze. Project fork to reproduce https://github.com/David-bfg/meteor-vue3 changes https://github.com/David-bfg/meteor-vue3/commit/1a10894619c01c7a777e67aede2f2828de8774a7

When using new syntax for

Note: error happens with all 3 components. (Counter, ScriptSetup, Info)

[Vue warn]: Failed to resolve component: Counter If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. at <App>

[vbgm]

Same problem here.

[vbgm]

Ok, it can be resolved with the pending PRs.

@Akryum would you be so kind to review and implement the pending PRs from @nathan-muir https://github.com/meteor-vue/meteor-vue3/pull/10 and https://github.com/meteor-vue/meteor-vue3/pull/11 ? This package desperately needs to be v0.0.2 :wink:

I understand you were focused on Vite + Meteor integration, and although it might sound a good idea for some complex situations (and I do use Vite for some other projects, but not in Meteor), but for simpler things normal Meteor builder works great. The biggest problem with Vite + Meteor btw, is that you can not use the same client entry point for Meteor and Vite, which is a no-go if you want to have modular architecture (keep your structure matching abstract logic, like having both client/ and server/ folders inside of nested structure within import/).

[vbgm]

Here is the working boilerplate of [email protected] + Vue3 + LessCSS with all the PRs included. https://github.com/vbgm/meteor-vue3-less