Module incompatible with recursive components about components

[bztest1]

same story if I use <component :is="myDynamicComponentName" />

[kevinmarrec]

Can people confirm that it works during SSR and then fails on client (hydration) ?

I've been able to see good output for less than a second, then when client is hydrated there come the error (hydration mismatching nodes error + unknown custom element)

[algoth]

@pi0 is there a workaround / fix for this. Stuck with this issue. Pls advice

[vampics]

+1

[simpsonphile]

+1

[davidturtle]

+1
My head is recursive now.

[LeCoupa]

@kevinmarrec Yes, it works during SSR but fails on client.

[LeCoupa]

I really love this package. Unfortunately, when you have a project with nested components, you have to revert back to basic imports. Just wondering if there is an ETA for fixing this issue?

[fabianwohlfart]

+ 1

I also get this error with a plain new nuxt installation and some super basic recursive data:

tree: [
        {
          title: '1',
          tree: [
            {
              title: '1.1',
              tree: [ /* etc */ ]
            }
          ]
        },
       ]

I get my recursive components working with putting the Item, in your case »CaseItem/Array/Object« to lazy: »LazyCaseItem/Array/Object«.
It (the html from it) also gets generated with npm run generate. Is this a safe option?

[StEvUgnIn]

Did anyone find any solution or should I downgrade my version of nuxt?

[LeCoupa]

@StEvUgnIn I think you should downgrade. This issue is not fixed yet.

[StEvUgnIn]

I am surprised that I meet this issue when I run my custom server based on express and spdy, but not with nuxt internal server...

[StEvUgnIn]

I fixed the bug in my project. It was due to babel transpilation. If you are using babel, make sure to disable it on Vue components.