Aleš
Aleš
Yea I know the reason, I just wonder whether is it intentional and what was the reasoning behind it..
On the other hand, I suppose that I should not even use portable when I want different widths for palm and lap.. but the thing is, I've added two more...
most likely a fault of the core, rather than the plugin, as it works for pipe, doesn't for directive
@CodeAndWeb except it's not the problem. See https://github.com/lephyrus/ngx-translate-messageformat-compiler#usage See also https://github.com/lephyrus/ngx-translate-messageformat-compiler/issues/20 
hm, I tried overiding the destroy event as suggested in https://github.com/DethAriel/ng-recaptcha/issues/123#issuecomment-426112101 and doesn't seems to have any effect
Otherwise, this is a great idea. 👍 Angular might take another year to do that cold observable thing.
Assign either `subject.asObservable()` or `subject` to the decorated property depending on the configuration option?
Or introduce second decorator `SubjectEvent`?
See https://github.com/fxck/template-streams-ondestroy-but for reproduction @d3lm 
Ok, I spent few hours trying to debug this. As soon as your `architect.build.options.aot` is set to true, this happens. Doing ```typescript ngOnDestroy() { super.ngOnDestroy(); } ``` makes it work...