Trying to document a external types package in a package that uses all of the types from that package

[MrJacz]

Gonna try and explain this as best as I can as ive spent a couple hours trying different ways to get this to work and have decided I might as well ask people who have done this already

So the package in question is https://github.com/lavacord/Lavacord/tree/exportwrappers specifically the exportwrappers branch as its the most up to date

the types package that I am using and also maintain is https://github.com/AmandaDiscord/LavalinkTypes/tree/main

So basically I want to have lavalink-types documented with my typedoc build, what I mean by this is, Where ever a type from lavalink-types is used in the Lavacord package on the documentation it should be clickable and direct to the documentation for that type, perferably I want lavalink types to be a seperate module on the docs

One thing I have found that i can do is

export * as LavalinkTypes from "lavalink-types/v4";

My problem with this is it just exports all of the types from lavalink-types to the lavacord package which is one way to do it I suppose it isnt exactly what im after

The other way I found I can do it but It still doesnt do exactly what I want is, add a entry path in typedoc.json to the lavalink-types package in node_modules and change entryPointStrategy to resolve

Any help would be much appreciated

[Gerrit0]

The other way I found I can do it but It still doesnt do exactly what I want is, add a entry path in typedoc.json to the lavalink-types package in node_modules and change entryPointStrategy to resolve

This is what I was going to recommend, what about this isn't what you want?

[MrJacz]

Sorry i shouldve explained that better, The only thing I dont exactly like about it is, instead of saying Lavalink Types on the docs build it says node_modules/lavalink-types/x/x/x

[MrJacz]

[MrJacz]

I have worked out if I put @module in lavalink-types main d.ts file typedoc will change it from node_modules/x/x/x to that module name