understanding-npm | A regularly updating survey of the npm community | Graphics library

I have a question regarding resolving types in my project. So basically I have packageA -> packageB-v1 -> packageC-v1, and I would like to use a type declared in packageC-v1 within packageA.

All packages are created by myself, and they are all typescript packages that generate declaration files by setting declaration: true in tsconfig.json file, they each expose multiple *.d.ts files in their dist folder. There is no corresponding @types/* package for types.

In this case, how should I import types correctly? So far I've tried:

1. import SomeType from 'packageB-v1/node_modules/packageC-v1/dist/SomeType'. This works, but I don't like that packageA needs to know where packageC is installed as it could change depends on package manage tool (npm/yarn), or the install orders (See https://medium.com/learnwithrahul/understanding-npm-dependency-resolution-84a24180901b). I've seen issues that due to different versions of packageC, the types are not the same and tsc is not ok with it. That could happen when there is another dependency like packageA -> packageB-v1 -> packageBB-v1 -> packageC-v2, where npm will install packageC-v2 instead of packageC-v1 under packageB/node_modules.
2. First export the necessary types SomeType from packageB-v1 by export SomeType from 'packageC-v1', then from packageA I can import SomeType from 'packageB-v1'. This works too, however, this also means packageB-v1 is on the hook to re-export all types from all of its dependencies (there could be many of them) that its consumers may need. That is not usually possible. Also, I've heard re-export may generate different types depends on each case.
3. In packageA's package.json file, add the dependency to packageC-v1 explicitly, even it's actually not directly depend on it. So we could use import SomeType from 'packageC-v1/SomeType. Unfortunately, this won't work either as we may have another dependency chain like packageA -> packageD-v1 -> packageC-v2. In that case, which packageC version we should install under packageA? This approach is bad also because even though typescript won't actually include packageC in generated JS bundle from packageA for using interfaces only, it may do that for enums.

The last way I haven't try is to create my own @types/packageC-v1 and publish it (and my other ts packages). However if I am writing these packages for a private org, that means we need to maintain an internal types repository, as well as maintain the paired versions of packages and types associate with them. Even if I managed to do that, I can still see many issues with this approach in terms of version mismatch, global declaration conflict, or namescope conflict (it is also true in the DefinetelyTyped/types approach).

I am not sure if these make sense to you, and really need some bits of advice here.