good job!
I was looking for a way to easily remove my store subscribers ...

I found this library because it was mentioned on SO:

https://stackoverflow.com/questions/38008334/angular-rxjs-when-should-i-unsubscribe-from-subscription

I really liked the idea of tackling this problem with an unobtrusive approach like decorators, but the approach you've laid out still seems like too much boilerplate (all the takeUntils). What if the decorator instead used AOP and wrapped subscribe calls, then you'd just need the decorator and the ngOnDestroy method? Did you consider such an approach?

When I try to build app with usage of AoT using Angular 5 and Angular CLI 1.5 I'm getting this error from angular2-take-until-destroy:
ERROR in ./node_modules/rxjs/observable/BoundCallbackObservable.js

From what I understand it may the problem of incorrect import from rxjs in library.

From what I learned at ReactiveX/rxjs#2304 the example in your readme should not work at all, since you only call complete() on the Subject, not next().

If there are multiple instances of the same component and one of those instances is destroyed, the current version of this decorator will kill the subscriptions across all instances even though they have not been destroyed.

I fixed the problem here but was unable to provide a PR as you only share your dist and not your source.

import { Subject } from "rxjs/Subject";
export function TakeUntilDestroy(constructor) {
    var original = constructor.prototype.ngOnDestroy;
    constructor.prototype._takeUntilDestroy$ = new Subject();
    constructor.prototype.componentDestroy = function () {
        return this._takeUntilDestroy$.asObservable();
    };
    constructor.prototype.ngOnDestroy = function () {
        original && typeof original === 'function' && original.apply(this, arguments);
        this._takeUntilDestroy$.complete();
    };
}
//# sourceMappingURL=angular2-take-until-destroy.js.map

It would be really helpful to get this in 🙏