You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to load different types of assets in templates and use Webpack plugins which aren't supported by Angular CLI out of the box. Right now my only option for customizing the compilation process is to fork the Angular CLI project and use my own custom version.
Would it be possible to expose configuration such that I'm able to inject my own Webpack plugin during the build process? If so, I could keep the surface area of my customizations small and support my use cases while also being able to respond to breaking upstream changes in Angular CLI.
I'm willing to flesh this idea out more and contribute a PR, but I'd be interested in getting people's opinions and would also like to know the current state of ongoing extensibility discussions and how this plays into them (#2906 for instance).
The text was updated successfully, but these errors were encountered:
I need to load different types of assets in templates and use Webpack plugins which aren't supported by Angular CLI out of the box. Right now my only option for customizing the compilation process is to fork the Angular CLI project and use my own custom version.
Would it be possible to expose configuration such that I'm able to inject my own Webpack plugin during the build process? If so, I could keep the surface area of my customizations small and support my use cases while also being able to respond to breaking upstream changes in Angular CLI.
I'm willing to flesh this idea out more and contribute a PR, but I'd be interested in getting people's opinions and would also like to know the current state of ongoing extensibility discussions and how this plays into them (#2906 for instance).
The text was updated successfully, but these errors were encountered: