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
{{ message }}
Repository navigation
Assets with the Same Name, but Different Path, are Copied Over Each Other #19850
Both images will be copied to the output directory with the same name, so you only get the dark or light logo, that will be used in both cases.
This won't be an issue on ng build --prod with "outputHashing": "all" or "outputHashing": "media".
This also won't be an issue on ng serve --prod, as per this comment, but will definitely slow down local debugging.
This could be fixed by using assets relative path (/assets instead of ../../../assets), but then it would be an issue on ng build --prod, since I don't include assets/images in assets in angular.json. The reason is that I don't want them to be duplicated (in assets and root folder), and this is by design, as per this comment.
🔥 Exception or Error
WARNING in Conflict: Multiple assets emit different content to the same filename logo.png
Activity
alan-agius4 commentedon Jan 22, 2021
Duplicate of #12186
angular-automatic-lock-bot commentedon Feb 22, 2021
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.