-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Element missing end tag in <NuxtWelcome /> component after recent update. #22383
Comments
I was also bootstrapping a new app this evening and run to the same issue. I can confirm that we have the same errors. I can reproduce and provide more context if needed.My case is in a local environment. |
I am having this issue on cloudflare's pages deployment as well |
Thanks. This was (likely) triggered by a release of |
For anyone looking for a workaround. Open this file. node_modules>@nuxt>ui-templates>dist>templates>welcome.vue Search the the following tag:
and replace it with:
Save and re-run the dev server script. |
The issue is resolved upstream in nuxt/ui-templates@0341634 and in the release of v1.3.1. You can pull this in by refreshing your lockfile or running the appropriate upgrade command for your package manager (e.g. I've raised an upstream issue in GoogleChromeLabs/critters#132. |
Environment
Reproduction
Somewhat surprising it hasn't been noticed yet but this bug is occurring in the StackBlitz environment linked on the Installation page in Nuxt's documentation https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
and locally when I attempt to do the following
Describe the bug
500 error caused by lack of end tag in
node_modules/@nuxt/ui-templates/dist/templates/welcome.vue
Seems to be related to 9741f26 and changes to
@nuxt/ui-templates
mixing withvite-plugin-vue-inspector
Safe to say I am not the only one experiencing this given it is occurring in one of nuxt's featured starter environments.
Additional context
Noticed this started happening when I build new nuxt applications in the past week or so and believe this coincides with these recent changes 9741f26
Here is a screenshot of logs from browser that were too long to post:
Logs
The text was updated successfully, but these errors were encountered: