Only document exported bindings

[arv]

My use case is that we have an index.js that forwards a bunch of bindings.

export {default as A} from './a.js';
export {foo, bar} from './baz.js';

Then a.js and baz.js might depend on other files that have different exported bindings.

What we want is to generate documentation for what is in index.js. For this --shallow does not work because we want to keep the jsdoc comments close to the binding declarations (and keeping methods etc in sync would be impossible). Having --shallow=false does not work either because then all annotated bindings gets exposed, even if they are not exported from index.js.

One way to achieve this might be to generate the json for everything and then manipulate that but it seems like this would be a valuable mode to expose.

[arv]

Thinking more about this.

Today the input/dependency.js generates a list of all files reachable by require/ModuleSpecifier. Then the code is traversed using an extractor. In this case it seem like this model is not a good fit and it would be better to let the extractor also determine which files to process.

@tmcw I would like your input on this topic since you have a better understanding of how everything interacts.