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 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:
For more information on the deprecation, check out the guide on the Ember Deprecations site:
For developers with a large number of themes/plugins, you may be interested in our mass-pr script to colocate templates.
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.
