# Handling the 'component-template-resolving' deprecation

**URL:** https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019
**Category:** Development
**Tags:** dev-news
**Created:** [June 13, 2025, 8:37am UTC](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019 "2025-06-13T08:37:56Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [June 13, 2025, 8:37am UTC](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019/1 "2025-06-13T08:37:57Z")

</div>

As part of our preparation for the Ember 6 upgrade, we have now enabled warning banners for the “component template resolving” deprecation.

 ![SCR-20250613-iunc](https://global.discourse-cdn.com/meta/original/4X/7/8/d/78dcdae1898d2d3e922bb6f5b2ea3886aa3e7c8a.png)

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]`

 ![SCR-20250613-iutc](https://global.discourse-cdn.com/meta/original/4X/c/a/e/cae466f7fc184792fc8450efb91a69a620749d86.png)

This message will include the name of the affected component (in this case `components/my-component`), which should help you to isolate the problem to a certain theme/plugin.

If the message refers to a `.hbs` component template in a theme/plugin’s `templates/components/` directory, then you should move the file from `/templates/components` to `/components`, so that it’s “colocated” with the component `.js` file.

If the message refers to a component template which has been defined in a theme via a `<script type="x-handlebars">` tag, then check out this topic:

> [@Modernizing inline script tags for templates & JS API](https://meta.discourse.org/t/modernizing-inline-script-tags-for-templates-js-api/366482):
>
> Using \<script type='text/discourse-plugin\> or \<script type='text/x-handlebars'\> in themes is now deprecated. Any use of these tags in themes should be updated according to the instructions below. Regular \<script\> and \<script type='text/javascript'\> are unaffected by this change. Timeline These are rough estimates, subject to change May 2025 - console deprecation messages enabled July 2025 - admin warning banners enabled Late September 2025 March 2026 - removal of feature Converting…

For more information on the deprecation, check out the guide on the Ember Deprecations site:

> **[Component Template Resolving | Ember.js - Deprecations](https://deprecations.emberjs.com/id/component-template-resolving/)**

For developers with a large number of themes/plugins, you may be interested in [our mass-pr script](https://github.com/discourse/mass-pr/blob/main/scripts/colocate-templates.rb) to colocate templates.

---

<div class="post-metadata">

### Author: ![Richie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/richie/32/115110_2.png) [@Richie](https://meta.discourse.org/u/Richie)
#### Post date: [June 13, 2025, 10:14am UTC](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019/2 "2025-06-13T10:14:00Z")

</div>

Thanks for the details @David😃

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [June 13, 2025, 2:02pm UTC](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019/3 "2025-06-13T14:02:33Z")

</div>

7 posts were split to a new topic: [When to switch themes/plugins to `.gjs`?](https://meta.discourse.org/t/when-to-switch-themes-plugins-to-gjs/370063)

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [June 13, 2025, 3:12pm UTC](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019/4 "2025-06-13T15:12:38Z")

</div>

> [@david](#):
>
> If the message refers to a `.hbs` component template in a theme/plugin’s `templates/components/` directory, then you should move the file from `/templates/components` to `/components`, so that it’s “colocated” with the component `.js` file.

Just to re-state this because I just can’t believe it. All you need to do (in the short term since we really want to jump on the `.gjs` bandwagon) is move stuff to the other directory? And then get rid of the templates directory? That’s awesome. I always hated those being in different directories.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [August 28, 2025, 2:57pm UTC](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019/5 "2025-08-28T14:57:30Z")

</div>

6 posts were split to a new topic: [Finding more info about the component-template-resolving deprecation](https://meta.discourse.org/t/finding-more-info-about-the-component-template-resolving-deprecation/380770)