Do not emit /// <reference types=".." /> for augmented declarations in dependencies

[mhegazy]

/// <reference types="node" />
interface I {
    e: Error;
}

> npm install @types/node

> tsc --d a.ts

> type a.ts

/// <reference types="node" />
interface I {
    e: Error;
}

Error should not be cause a type dependency as it partially came from lib.d.ts

[jayphelps]

RxJS member here, any ideas how we can work around this as a library author, so our users don't have to? (as we wait for 2.1) ReactiveX/rxjs#2112 It looks like we misunderstand what the real problem is--we thought we fixed it in ReactiveX/rxjs#2120 but turns out we didn't.

Since I don't see hundreds of devs yelling in this thread about this, perhaps there is something we're doing we can avoid? We could build RxJS with canary/dev release, but we'd prefer not to for risk of adding other bugs as well.

[mhegazy]

you can strip out the /// <reference types ... /> from the resulting .d.ts files, wouldn't this be sufficient?

[jayphelps]

@mhegazy oo just go in by hand and remove them from the artifacts, before we publish? A crude but hilariously effective solution.

[mhegazy]

you just need a regex.

[mhegazy]

alternatively 2.1 RC should have the fix for the issue.

[rightisleft]

Sadly using @jayphelps approach to fixing this bug until next RC ....