# Component template resolving pink banner
**URL:** https://meta.discourse.org/t/component-template-resolving-pink-banner/369978
**Category:** Support
**Created:** [June 13, 2025, 1:26am UTC](https://meta.discourse.org/t/component-template-resolving-pink-banner/369978 "2025-06-13T01:26:16Z")
**Posts on this page:** 1
**Showing post:** 10
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [June 13, 2025, 8:41am UTC](https://meta.discourse.org/t/component-template-resolving-pink-banner/369978/10 "2025-06-13T08:41:51Z")
I’ve just posted a dedicated topic for this deprecation, and I’ll update the warning banner to link there instead of taking people directly to Ember’s docs.
> [@Handling the 'component-template-resolving' deprecation](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019):
>
> As part of our preparation for the Ember 6 upgrade, we have now enabled warning banners for the “component template resolving” deprecation. To find more information about the issue, open up the browser developer console (F12), and look for a message including [deprecation id: component-template-resolving] This message will include the name of the affected component (in this case components/my-component), which should help you to isolate the problem t…
> [@Lilly](#):
>
> you should disable them until they are fixed. see here:
To expand on this: disabling them will remove the error banner, so that’s fine if you really need to hide it.
But it’s worth noting that deprecation notices don’t mean something is broken. It means that it will be broken in future, and we’re giving developers some advanced warning of that. It’s fine to keep using these things in the meantime.
On the `