[learn.nuxt.com] Cannot read properties of undefined (reading ‘default’)

[raminjafary]

@antfu I think this is a common issue across all websites using Nuxt. You just need to search couldn't resolve component at in google to see the scale of impact.

Related: nuxt/nuxt#29624 (comment)

[jeannen]

Same issue here on multiple websites

[antfu]

On my side, it works fine?

nuxt/nuxt#29624 looks quite severe, we would love to fix as soon as we can, however with all the information provided in the thread, it seems quite random and related more to CDN/network infra than on our side?

[raminjafary]

I think the issue might be, while navigating between routes and there is a new release, the chunk errors are not properly caught in the chunkError handler to emit chunk error event and to apply the intended strategy but instead execution continues resulting in a crash.

[kemchenj]

On my side, it works fine?

nuxt/nuxt#29624 looks quite severe, we would love to fix as soon as we can, however with all the information provided in the thread, it seems quite random and related more to CDN/network infra than on our side?

@antfu Please try search with this query site:nuxt.com Couldn't resolve, it is still exist.

[jeannen]

Any update on this? :/