-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to resolve component replacing blaze with static-html #8
Comments
Same problem here. |
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 #10 and #11 ? This package desperately needs to be v0.0.2 😉 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/). |
Here is the working boilerplate of [email protected] + Vue3 + LessCSS with all the PRs included. |
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 David-bfg@1a10894
When using new syntax for <script setup> components are inaccessible.
Note: error happens with all 3 components. (Counter, ScriptSetup, Info)
The text was updated successfully, but these errors were encountered: