Module-added component throws 'src.replace is not a function' if prefixed with Lazy and is not a vue file

[smastrom]

Environment

Stackblitz

Reproduction

https://stackblitz.com/edit/nuxt-starter-5f85qa?file=app.vue

Describe the bug

Given two components that produce the same output:

JsComponent.js

import { h, defineComponent } from 'vue'

export const JsComponent = defineComponent({
  render() {
    return h('div', null, this.$slots.default?.())
  },
})

VueComponent.vue

<template>
  <div><slot /></div>
</template>

Added to the Nuxt app via addComponent in a Nuxt module definition:

addComponent({
  name: 'JsComponent',
  export: 'JsComponent',
  filePath: resolve('./JsComponent.js'),
})

addComponent({
  name: 'VueComponent',
  filePath: resolve('./VueComponent.vue'),
})

If prefixed with Lazy:

<template>
  <LazyVueComponent>Hello</LazyVueComponent>
  <LazyJsComponent>Hello</LazyJsComponent>
</template>

The .vue one works as expected, the .js one throws the following SSR error: src.replace is not a function.

After dealing with this a bit, I found out that if the js component has no child, it doesn't throw any error:

<LazyJsComponent></LazyJsComponent>

But even a single char or a comment will break things again.

Additional context

No response

Logs

[Vue warn]: Invalid vnode type when creating vnode: undefined.
[nuxt] [request error] [unhandled] [500] src.replace is not a function

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• nuxt-starter-5f85qa (Open reproduction)

[huang-julien]

hmmm seems like doing a default export in the JS file can be a workaround. Will take a look a bit later 🤔 .
Not sure if it's a vue core or nuxt bug atm

[Xzandro]

I encountered a similar issue with dynamic components that have a slot.

<component :is="components[block.__component]" :block="block" :page="page">
   <Headline/>
</component>

Will throw the exact error message. Even when I set a simple string instead of the headline component, it will cause this error. Kind of blocking for me, is there any workaround for this? I could wrap these in <ClientOnly>, but this defeats the purpose of SSR.

[Xzandro]

When using my case, this unfortunately does not fix the error even on nuxt 3.10.0.

[danielroe]

@Xzandro would you create a new issue with a reproduction? 🙏