Failed to generate dynamic story source: TypeError: can't access property "_vnode", storyNode is null

Describe the bug The bug coming like this in my app, where it supposed to not appearing in @nuxtjs/storybook v.3.2.0 or before related 6.1.4. I thought its affect to the docs stories that won’t load before, but i’ve configured it again. and now its loaded perfectly. and but then, it keeps showing error :

Failed to generate dynamic story source: TypeError: can't access property "_vnode", storyNode is null

To Reproduce Steps to reproduce the behavior:

1. I already configured the stories and config, and also no any indication error in chromatic test as well,
2. each time i press on selected stories, the warn log keep adding, and its adding again when visit another stories.

Expected behavior No any warning log appearing each time selecting stories

Screenshots If applicable, add screenshots to help explain your problem.

you can try it, in my open source deployed app here : talkiebuddy.github.io/talkiebuddy-ssr-app

[alfredgm45]

@ahmadalfy in my case this error happened when I was creating a decorator and I was using the render function ex:

export default makeDecorator({
  name: 'darkMode',
  parameterName: 'dark',
  wrapper: (story, context) => ({
    render: h => h(story(context))
  })
})

and the solution was adding Vue.extend

export default makeDecorator({
  name: 'darkMode',
  parameterName: 'dark',
  wrapper: (story, context) => Vue.extend({
    render: h => h(story(context))
  })
})

the error "Failed to generate dynamic story source: TypeError: can't access property "_vnode", storyNode is null" happens in the first code case, because in the wrapper property I was passing a vue instance, and this needs to be attached to an HTML element to be mounted, so for that reason the storyNode was null, in the second case, well, Vue.extend creates a “subclass” of the base Vue constructor, and when this new constructor is called, this returns a VueComponent, this can be used in any parts of your app.

I hope, this can help you. 🙂

[ahmadalfy]

@fbtwitter did you find a way to fix this? I am having the same problem