View Full Version : Angular CLI and Webpack Config

25 Feb 2019, 9:50 AM
First off, this is a great project and could be very useful for us. However there’s one challenge that I’d like to bring up.

At my organization, we have standardized on using the Angular CLI. This means we do not manage our webpack configs manually. We went through several very painful years of manual webpack management and decided after several time-intensive breaking upgrades (of either angular or webpack), it is just better to leave it to the CLI and keep the management of webpack out of our dev ops process altogether.

We really don’t want to have to go back to managing webpack manually. Is it possible to make Ext-Angular work without the required webpack plugin? What does it do exactly? If this is not a possibility, I hope we can see some upcoming documentation or examples for those of us using Angular CLI exclusively — specifically the process of creating a custom webpack config and integrating it with an existing angular cli generated project. Thanks!

4 Mar 2019, 8:33 PM
Thank you so much for your post. I apologize for the delay. I have shared this with the support staff to look into at their earliest convenience. Your patience is greatly appreciated! We do suggest using the support portal when you need assistance with a capability of a Sencha product, you have identified a situation where a products behavior is inconsistent with the product documentation and might indicate a software bug, or when the communication between you and Sencha needs to be private.

Thanks again,


16 Apr 2019, 2:37 AM
although the webpack plugin is very helpful in managine the ExtAngular components, you can configure your Angular-cli project to not need it. I will put together an example project and post it to the githum repo

18 Dec 2019, 11:39 AM
Hi, is there any update on this thread. We would like to use ExtAngular within an existing Angular app that is generated and handled by the Angular Cli.
Going through the tutorials there are requirements to change webpack config file, which is not existing in the project eventhough we installed the dependencies per the tutorial recommendation.
Can you provide some help to bypass that ?