No externs are generated for re-exported namespace

[theseanl]

As I understand tsickle does not support generating externs from export * from '...' syntax (which I couldn't find a tracking issue), but it seems that it does not support externs generation for the following situation as well:

import * as foo from 'bar';
export {foo}

[evmar]

(Edit: deleted comment above that wasn't about this specific bug.)

[evmar]

In general, I believe tsickle doesn't support imports or exports within externs at all. I think there's a more general bug in the tracker that is about this problem, that this might be considered a dup or a subtask of. We don't really have a good conception of how to even represent this, given that externs files themselves can't have import/exports.

[theseanl]

We don't really have a good conception of how to even represent this,

Isn't a module .d.ts just externs declared on some namespace? It is the idea I've learned from tsickle.

I believe tsickle doesn't support imports or exports within externs at all

Module .d.ts already work 90% of time. Given that almost all declaration files in DefinitelyTyped are module .d.ts, IMO making it more complete would open a lot of use cases.

[evmar]

We definitely would like this to work, we just haven't had time for it. I think you're right that hiding things on a namespace works for a single file, but I'm not sure whether all the various other interactions do the right thing with it.

[evmar]

(Part of the reason we haven't worked on this much is that we don't have a good model for using third-party dependencies in JSCompiler even when there is no TS involved.)

[theseanl]

I'm not sure whether all the various other interactions do the right thing with it.

Huh, I thought it is already doing the right thing most of time. If you have some particular concerns I'd like to know, I am willing to work on this issue and provide a PR.

[evmar]

Sure, send a PR for this if you have a fix.