Shlomi Assaf

Hi guys Most of the hard work for supporting multiple libraries is around mapping. Each library must map to its public import token, so other libraries and the demo app...

If you don't want to use scripts it means you want the users to write those mapping definitions and all other complex configurations. This will not work, it's advanced and...

The reason each tool works differently is simple, they are built by different teams and for different purposes. Webpack is a bundler, TypeScript is a compiler so they might have...

The plugin essentially move things from there to there, the core functionality is in the angular compiler. Can you please give more details on the setup and project, maybe something...

Angular 5 will introduce lots of changes... Possibly an AOT watch mode and more... I'll try to explore and see what we can add/improve

Bad news, they have changed the whole process, it's completely different. They have watch mode built in the compiler now which changed everything... I'll have to assess it and see.

You can use @gregbown [workaround](https://github.com/shlomiassaf/ngc-webpack/issues/32#issuecomment-335189013) for now. It means that: - If you used one of `ngc-webpack` hooks you cant now - You can not use a typescript loader (e.g....

OK, I'm trying to get to the best solution here and the situation is tricky and complex. **I'll need you input here** ### Some background: - This plugin was built...

Well, the solution is not optimal but not so bad. Reason is, the compilation is done by angular/compiler and the angular/compiler-cli is just the engine that runs it. So yes,...

Hi guys, Thank you all for the support! I have refactored `ngc-webpack` to support angular 5 using `@ngtools/webpack` instead of `@angular/compiler-cli`, this allows keeping the extra features in `ngc-webpack` with...