-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.../node_modules/vuepress-jsdoc/node_modules/.bin/vue-docgen: not found #44
Comments
I think maybe you should find the executable on the |
Thanks for reporting. It would be nice, if you can attach a zip or something else, with a minimal reproduceable example. |
Hi @ph1p sorry for my delay I was very busy these days, here is the repository https://github.com/diegoazh/vuepress-jsdoc-issue, use the script |
Thank you! Now it should work. I also dropped 3 dependencies. Version |
Excellent, thank you @ph1p I will test it this weekend. |
@diegoazh In the meantime I have rewritten a lot :D It would be great if you could check if |
@ph1p, yes I installed the last version and it works like a charm, thank you so much for the effort 🎊 🎉 |
Describe the bug
I found the above error in the last version, for some reason
vue-docgen-api
is not installed inside of thenode_modules
of thevuepress-jsdoc
, I'm not sure why but when it try to use it to generate the docs in line145
ofcmds/index.js
it isn't there.I add prints to the modules inside of the
node_modules
invuepress-jsdoc
and thenodeModulesPath
androotProjectFolder
variables in the first and second screenshots in the last screenshot you can see the error.../.bin/vue-docgen
module not found.To Reproduce
Steps to reproduce the behavior:
install
vuepress-jsdoc
and run the command to generate the documentation.Expected behavior
Works in the same way as version
3.2.0
worked.Node (please complete the following information):
14.17.1
Additional context
I had installed
vue-docgen-api
andvue-docgen-cli
in mydevDependencies
but, I remove them from mydevDependencies
and I made a fresh install with a newpackage-lock.json
generated and the error is still happening.The text was updated successfully, but these errors were encountered: