Components loading failing with using the content module

[kalinichenko88]

Describe the bug

In dev mode all works. But nuxt generate and nuxt build failed with the error

• If a component is registered in the page it will work fine
• issue with autoloaded components only
• I solved this issue for myself. I added in package.json "@nuxt/components": "2.1.8"

To Reproduce
Steps to reproduce the behavior:

1. Clone repository https://github.com/kalinichenko88/nuxt-components-bug
2. Run npm i
3. Run npm run generate
4. See error Error: render function or template not defined in component: tutorial

[chrispreisler]

I also experienced the same bug, when using the plugin with dynamic components like this:

    <component
      :is="componentName"
      :data="story.content"
    />

I stepped back to 2.1.8 with yarn resolutions like this:

"resolutions": {
  "@nuxt/components": "2.1.8"
}

There I don't have any problems. It is also only happening, when building/generating the page.

[rchl]

I'm using undocumented components: { loader: true } in my nuxt-config and with that the https://github.com/nuxt/components/releases/tag/v2.2.0 appears to have a breaking change. Most likely due to:

• explicit async loading (feat: explicit async loading #212) (5adefb9)

Even more annoying that it doesn't trigger in development so the issue is only discovered after deploying.

[chrispreisler]

Yes, I also think, that this feature may be a breaking change for dynamic components. I also tried adding async to the filename, but this doesn't work either.

[rchl]

I'm getting errors like: ERROR render function or template not defined in component: foo-bar-v-2 with the new version.

What would be a way to get things to work for someone who uses loader: true (apart from downgrading)?

[pi0]

Thanks for reproduction @kalinichenko88. Just remove package-lock.json (or yarn.lock) and reinstall dependencies. The issue is fixed in v2.2.1.

[ibdf]

I am still having this issue, but it fails without an error. The vue component in the .md files load perfectly in the dev environment but not when using generate or build. I am on:

"@nuxt/content": "^1.11.1",
"nuxt": "^2.14.12"

components: true

Update: Switched from using components: true to components: { loader: true } as mentioned previously above and that actually fixed it for me.