Similar issues - #28060 - nuxt/nuxt - unsight.dev

# Docs (useNuxtData => #Optimistic Updates).Incorrect Use of Reference Assignment in previousTodos.value = todos.value

Docs (useNuxtData => #Optimistic Updates).Incorrect Use of Reference Assignment in previousTodos.value = todos.value

nuxt/nuxt.com · updated7 months ago · 36% similar

conflict with @vue-macros/nuxt 'Type warnings'

nuxt/ui · closed2 months ago · 34% similar

bugv3triageclosed-by-botstale

NuxtLink with custom directive is throwing console warning

nuxt/nuxt · closed1 year ago · 34% similar

bugpages🔨 p3-minor

If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.

nuxt/nuxt · closed3 years ago · 34% similar

3.xpending triage

runtime-core.esm-bundler.js:38 [Vue warn]: Failed to resolve component: nuxt-child If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.

nuxt/nuxt · closed3 years ago · 34% similar

3.xpending triage

Issues with the Vue runtime compiler support

nuxt/nuxt · closed3 years ago · 34% similar

3.xpending triage

node_modules component in nuxt modules : I still get SSR related errors despite `mode:client`

nuxt/nuxt · closed2 years ago · 33% similar

3.xpending triage

Failed to resolve component in pages

nuxt/nuxt · closed3 years ago · 33% similar

3.xpending triage

add support for configuring @vitejs/plugin-vue-jsx's isCustomElement option

nuxt/nuxt · closed3 years ago · 33% similar

3.xvite🍰 p2-nice-to-have

Failed to resolve web component warning

nuxt/nuxt · closed2 years ago · 33% similar

3.xpending triageneeds reproduction