Younes Jaaidi

I didn't know about `@ngneat/loadoff`. It's in fact, quite similar. Though, by peeking on the source code, the behavior is slightly different. In fact, `suspensify`'s `finalized` is set to true...

Hi everyone, In fact, `@wishtack/reactive-component-loader` is highly coupled to `ng-dynamic-component` as it is meant to inject & lazy load components with one single directive. I only saw three possibilities at...

Hi Alex, I think that https://github.com/gund/ng-dynamic-component/issues/245 is related to this issue. `@wishtack/reactive-component-loader` lazy loads components on demand which could be inserted using `ngComponentOutlet` but in order to pass inputs and...

Hi Alex, Thank you for your detailed review. Actually, extending `DynamicDirective` was the first thing I experience and I don't really remember why it went wrong and end up with...

Oh! Now I remember the limitation I met. I need to inject `ReactiveComponentLoader` service. That would look something like this: ```typescript @Directive({ selector: '[wtLazy]', }) export class LazyDirective extends DynamicDirective...

Hi Alex, thank you very much for your help. The idea is brilliant!!! I tried it but I encountered the following issues: ### 1. `LazyDirective` injection issue I guess you...

It's using the Angular CLI common webpack configuration. In the really short term, we will add an optional target option to choose the configuration to use from Angular.json in order...

Hi @philippjenni, this is in fact an interesting feature that we didn't dive into yet. We would be more than happy if you or anyone else could help us out...

Hi @Heines1983, sorry for responding so late. Concerning your first issue, this is actually related to the fact that you are using a synchronous access `[0]` on `getItems()` return value......

Hi @parky128, which version of html-webpack-plugin are you using?