-
Notifications
You must be signed in to change notification settings - Fork 22
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
Astro/Vite fails to properly mount Vue #18
Comments
Here's a minimal reproduction on Stackblitz |
Thanks for the detailed bug report @kcole93! I'm wondering if this is due to this integration also installing |
Hi Chris, just a heads up that someone else in the Astro discord came across a similar issue with weird Vue errors that were fixed when the order of declaring Vue in See Issue 4994 in the Astro repo. |
Thanks for the heads up @kcole93 — appreciate it! In that case I think we can close this issue. If anyone else finds themselves here, looking for a quick solution: try moving |
After installing astro-netlify-cms and adding a basic config entry in
astro.config.mjs
, Vue components failed to render as the Vue instance was seemingly not being properly mounted.Fails to render Vue components
Properly renders Vue components
I'm not sure if this is an issue specific to the Astro-Netlify-CMS integration, or if it's on the Astro / Astro Vue integration side of things. However, it was difficult to figure out the cause other than that it having occurred after setting up Astro-Netlify-CMS.
In case it helps to identify the source, here's the error messages I was getting.
When rendering Vue components without a client directive:
[plugin:vite:vue] Attribute name cannot contain U+0022 ("), U+0027 ('), and U+003C (<)
When they are passed a client:only directive:
Vue warn: Component is missing template or render function
Perhaps it's worth mentioning in the installation / config instructions that this can be resolved by declaring the Astro-Netlify-CMS integration prior to Vue.
The text was updated successfully, but these errors were encountered: