Angular-cli: Angular CLI production build placing duplicates of all my fonts in the root of my dist directory. Can this be avoided?

[ahirhasmukh]

Do you have any solutions?

[Brocco]

Please either update this issue or create a new issue following the new issue template. Thank you!

I also suggest checking out this article in the documentation: https://github.com/angular/angular-cli/wiki/stories-asset-configuration

[vimalraj-a]

Bug Report or Feature Request (mark with an x)

• [ ] bug report -> please search issues before submitting
• [x] feature request

Versions.

ng version : 1.2.0
NPM: 5.3.0
Node: 6.11.0
Windows 10

Repro steps.

Simple steps to reproduce this bug.
ng build --prod --aot=false -bh=./ -d=./resources
-d is for specifying the publicPath. It changes the url() in css files but actual files are not in resources directory.

The log given by the failure.

NA

Desired functionality.

What would like to see implemented?

Separate folder or use assets folder for fonts and images referenced in css/less/sass files.

What is the usecase?

We are using font-awesome, kendo like other 3rd Party libraries in our project. Using Angular CLI we are creating production build.

Angular CLI emitting all referenced resources like jpg|png|webp|gif|otf|ttf|woff|woff2|cur|ani into root folder of the distribution.

Can these files placed in assets or configurable folder names?

Mention any other details that might be useful.

[GeorgeKnap]

this issue should be reopened.

[naviegodenavia]

any solution? The same thing happens to me with images as well as with the sources

[niravjadatiya]

facing this same issue

[shoudaos]

The same issue

[tmdevries]

I am also experiencing this issue. CLI version is 1.7.0

[lucaritossa]

I think this is a duplicated of #6599

[blazejpawlak]

@vimalraj-a have you found a solution or a workaround to your problem?

[abdullah2993]

This issue should be reopened, and https://github.com/angular/angular-cli/issues/6599 too

[lmperezCuba]

I have the same problem with fonts and images.

[clydin]

That's actually not a problem as that is the intended behavior. If preferred, the resourcesOutputPath build option can be used to place the resources in a directory.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}