Barthélémy Ledoux

Would this setup help anyone here? https://github.com/elevatebart/test-nuxt

Conceptually, cypress Component Testing and vue-styleguidist work the same. Since each component is displayed in isolation they lack a common root. In a proper app, this root is called `main.js`....

@davodaslanifakor without a reproduction repository, it is very hard to diagnose what is happening. Using Nuxt + tailwind + styleguidist is done in [this example repo](https://github.com/elevatebart/test-nuxt) and it seems to...

it is an error in https://github.com/salesforce-ux/theo As a work around you can install optimist yourself.

Hey @ljelewis, I believe I found a way to implement your use case here: https://github.com/vue-styleguidist/vue-docgen-api/pull/120 please review ;)

@viljamis, @HerrBertling I think it might be a grand idea, I just need to revert the switch to yarn since it is not necessary for this change. Let me revert...

Hi @viljamis, I removed entirely the references to yarn from this branch. I hope yuou find the comments here useful. If not please advise. Yours, bart

Hey @emptyfortress , This might very well count as a bug, in [react-styleguidist](https://github.com/styleguidist/react-styleguidist) where the search component is built. I know that Artem Sagepin speaks russian @sagepin do you think...

This is where the component is made : [TableOfContentsRenderer.js](https://github.com/styleguidist/react-styleguidist/blob/master/src/client/rsg-components/TableOfContents/TableOfContentsRenderer.js)

Thank you @ericraio This issue can be annoying indeed. @viljamis, I believe [this PR](https://github.com/viljamis/vue-design-system/pull/206) should fix it. What do you think?