-
Notifications
You must be signed in to change notification settings - Fork 179
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
Integration with VitePress? #287
Comments
Sure will take a look...Without plugin life-cycle hooks it will make it more of a manual setup but can look into best way to integrate. Need to update the docs to explain properly how to extend the themes too. |
Hi Tom, just FYI, we were able to generate something automagically with a script here (thanks to @ST-DDT effort) but not sure if that's useful for you or if there is any way to integrate that back to your repo? It's indeed very manual-ish, as you said, as it seems there are no more hooks we can attach this to in Vitepress. |
It is possible to create vitepress plugin as vite/rollup plugins |
Any updates or is it possiable for vitepress? |
If still of interest have created a theme that will preset options for use with VitePress and generate a sidebars file: https://github.com/tgreyuk/typedoc-plugin-markdown/tree/next/packages/typedoc-vitepress-theme#readme . Requires pre-release versions to be installed. |
Do you have screenshots or a demo deployment for reference purposes? |
I will set up a demo repo. |
Hi, I am interested in a demo too @tgreyuk I tried setting up a repo according to instruction here: https://github.com/tgreyuk/typedoc-plugin-markdown/tree/next/packages/typedoc-vitepress-theme#readme but I get
I guess Is that a specifc version ? |
anyone could get that working ? Edit: Actually for some reason, I was not on latest "next" version. after fixing this, I got it working. Thanks ! |
I was getting the same error with both the latest @next versions ( "typedoc-vitepress-theme": "1.0.0-next.0",
"typedoc-plugin-markdown": "4.0.0-next.11" |
@tgreyuk This is a difficult question to ask because it often comes across as needy or demanding, but it's purely a strategic question. Dealing with No one has a crystal ball, so the answer of "idfk" is totally an acceptable answer 😂 But are we anticipating any major changes / overhauls between now and whenever this makes it to an official 1.0 release? Or is it looking pretty stable for now? Again, no rush. Loving the work that's being done here, and super excited to use it. We have an immediate need for it, so we're going to go ahead and start using it, and we can provide some "beta tester feedback" for anything that we run into to help contribute as we start playing around with it. But I was thinking about throwing some stories in our backlog to anticipate breaking changes if you think you might refactor major pieces of it 🙂👍 |
Hi @Swivelgames, Thanks for asking the question and I'd like to say things are quite stable now after some recent breaking changes. The plugin simply breaking shouldn't happen again as there are some tests on the CI now. There may be a couple of option tweaks but that's about it. My main focus now is on stability and documentation, contributing guide etc. It would be great if you could start using it and provide feedback. I can normally fix things pretty quickly and happy to look into any feature requests. A couple of links of interest:
|
Thanks!
|
Released: typedoc-plugin-markdown@4.0.0 |
VitePress has a different way of handling plugins. Plugins are now in Themes.
As we wanted to use TypeDoc and VitePress for the documentation of Faker.js, we were wondering what would be the best approach for that? Do you see this as a quick fix or should we create a new Vitepress theme by contributing to your repo maybe?
The text was updated successfully, but these errors were encountered: