Angular component library – image references in templates

All we need is an easy explanation of the problem, so here it is.

I have an npm package that has a number of angular components. In their templates, they reference images. If I copy the images to my application’s images directory, the references resolve, but this feels stupid.

Is there a way to have webpack handle image writing so that when App B includes components from App A, the images work in the build and there’s no manual copy step involved?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

If images are not properly required in this npm package then webpack won’t be able to process them. You may try something like copy-webpack-plugin or write own copy script to avoid manual copying

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply