Nested Namespace imports not working

[AjaniBilby]

This might be out of the scope of this project, but I am trying to use this to generate searchable docs for all functions within a large private repository.

So I wrote a script which generates barrel files, so I can just reference one of those as the entry point
i.e.

export * as Component from './component/mod.ts';
export * as Model from './model/mod.ts';
export * as Util from './util/mod.ts';

But it ends up buliding only accessing one layer deep. (deno doc --html mod.ts )

However if you barrel without namespace it it does then work properly, however you can then have namespace collisions if you have multiple functions with the same name, where the context of which file they are in is what's important.

// app/util/mod.ts
export * from './color.ts';
export * from './format/mod.ts';
export * from './math.ts';

Also when I try and point deno doc at multiple of these mod files you end up with a lot of broken relative links (plus it doesn't help with heavily nested folders).

deno doc --html ./app/util/mod.ts ./app/component/mod.ts ./app/model/mod.ts

---

I've created a small sample repository so this can be easily reproduced.