Cross-package references in monorepository not working
See original GitHub issueSearch terms
monorepository entrypointStrategy packages reference
Expected Behavior
Cross-package references should “work” when generating documentation for several packages in a monorepository (using yarn workspaces), with an entrypointStrategy
set to packages
.
Actual Behavior
Cross-package references yield a warning:
A, defined at packages/a/lib/index.d.ts:3, is referenced by @typedoc-packages-missing-export/b.B.__type.a but not included in the documentation.
And the resulting documentation does not have hyperlinks for such references.
Steps to reproduce the bug
Here is an example repository to reproduce the bug: https://github.com/nlepage/typedoc-packages-missing-export
Environment
- Typedoc version: 0.22.10
- TypeScript version: 4.5.4
- Node.js version: 14.17.0
- OS: Linux
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Compile multiple packages in a mono-repo in a single ...
A project I'm working on (a fairly large monorepo) is not yet able to upgrade to use project references, and until very recently...
Read more >Cross-repository Component Sharing using Mono-repo Multi ...
Mono repo means that you will end up with multiple projects as packages within the same git ... Using a monorepo we can...
Read more >Simple monorepos via npm workspaces and TypeScript ...
In this blog post, we'll explore how to set up a simple monorepo for two npm packages. All we need is already built...
Read more >What am I missing in this TS mono-repo setup? - Stack Overflow
I've been struggling to get this TypeScript npm monorepo bootstrapped. My goal is to have various "packages" which I can cross import from....
Read more >Working with monorepos - Expo Documentation
Monorepos, or "monolithic repositories", are single repositories containing multiple apps or packages. It can help speed up development for larger projects, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @Gerrit0
I made a plugin to solve the problem: nlepage/typedoc-plugin-resolve-crossmodule-references. Not sure about all of it, but it works fine for the basic cases. Here is an example of generated documentation where types from a module
a
reference a typeB
from a moduleb
. It is published on npm.I’m not sure if it can help with project references as I’m not familiar with these.
Let me know if it is something you would like to integrate in TypeDoc itself. It needs only one new dependency (plus a transitive one): convert-source-map.
@phihochzwei I published a new release of the plugin, let me know if it works for you.