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] 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] 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 tag, then check out this topic: [image] Modernizing inline script tags for templates & JS API Development Using or in themes is now deprecated. Any use of these tags in themes should be updated according to the instructions below. Regular and 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 For developers with a large number of themes/plugins, you may be interested in our mass-pr script to colocate templates.

Thanks for the details @David :smiley:

[image] 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.

Handling the 'component-template-resolving' deprecation

Development

Topic		Replies	Views
Component template resolving pink banner Product Support	12	575	June 16, 2025
How to track down `(id:discourse.component-template-resolving)` Product Support	5	277	October 22, 2025
Finding more info about the component-template-resolving deprecation Product Support	8	409	August 28, 2025
How to find item needing update? Product Support	3	280	June 16, 2025
How to identify which theme/component/plugin needs an update? Product Support	1	241	June 15, 2025

Handling the 'component-template-resolving' deprecation

Related topics