-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support for the Typedoc 0.26 #16
Comments
Did you run into any problems with the new TypeDoc version? I'm not planing to update the plugin until TypeDoc 0.26 is officially released. |
The peer depedencies don't have 0.26.x set so npm refuses to install it normally, and I fear i'll break something using legacy-peer-deps or force |
Yeah, there is a reason I was defensive with defining the peer dependencies. Most major updates broke my plugins. What do you think would break if you force the update? Btw. you could change this line in your |
I stopped beeing able to click classes and their icons dissapeared, it also didn't actually merge them |
I was unable to get this plugin to work with the packages entry point strategy, FYI. I plan on getting a minimal reproduction up today. Edit: My bad, I see that was released in 0.25.12. I'll open a different issue if needed. |
Hi Ben. You can find examples for monorepo setups (using the "packages" entry point strategy) in the test folder here on GitHub: https://github.com/krisztianb/typedoc-plugin-merge-modules/tree/master/test Please take a look and compare your setup. If you still think that there is an issue with the plugin please open another issue. Thank you. |
Appreciate it, will do. |
TypeDoc 0.26 has been released and I can confirm that the plugin is no longer working correctly. Will have to debug the problem. |
I published version 6.0.0 which should work with TypeDoc 0.26.x Please try it and report back if you find any issues. Thank you. |
seems to work |
I am using the Beta for the packageOptions property of tsconfig.json, but would prefer if the modules were all under the name of the Module like this plugin does, is there any way I could use it with 0.26.0-beta.2?
The text was updated successfully, but these errors were encountered: