# 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:** 1\
**Showing post:** 4

<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.

---

_[View the full topic](https://meta.discourse.org/t/handling-the-component-template-resolving-deprecation/370019)._