Closed earthtone closed 5 years ago
Hey @earthtone, have a looksie at this bug vue-styleguidist/vue-styleguidist#191.
I believe this would solve your ignore problem.
As soon as @rafaesc has released vue-styleguidist
I will release an updated version of the plugin.
I am investigating the same babel issue in my repo. It seems to be due to the use of jest and its delayed update to babel 7. Still looking into it.
Okay, I'll run some tests to try to help you. 😁👍
Just pusblished v0.1.3 with the ignore fix
Vue-docgen-api was updated, but cli version oldest.
Solution: install vue-docgen-api manualy
yep, I need to deliver an update. Thank you for the feedback.
Hey @earthtone, Do you mind if I close this issue as it seems to be fixed and delivered?
Running the styleguide script (to run the styleguide from a local server) after updating from version
0.1
to0.1.2
throws the following error:After commenting out the
ignore
configuration option, running the script works, but logs the following warning:The styleguide is then able to be generated as expected, without the first component indicated in the warning, regardless of what that first component is. I've tried excluding several components now, which is not easy considering the
ignore
option is no longer supported, and I get the same warning pointing to whichever component is the first to be ingested by the plugin.I'm trying to include this in a project generated with
vue-cli v3.0.1
with these config options, scripts & dependencies. Is there some conflict in my project I should be aware of? Is there a less invasive way of addressing these errors and warnings, since this is an organization project and I do not have a lot of freedom to update dependencies wildly.If this is not a genuine bug I'd personally consider an API change and a dependency update that requires consumers to update their projects' dependencies a breaking change, not a patch, as indicated by the update in version number.