David, are there plans to cease support for “split” components and “non .gjs” at some stage?

Probably yes. It looks like separate js/hbs will be supported by ember for the foreseeable future, but it may make sense for us to make a move earlier to simplify our theme/plugin build systems. If we do decide to deprecate hbs, we’ll go through all the normal deprecation cycle and announcements, so it won’t come as a surprise. For themes/plugins using our standard linting config, .hbs files are already banned, and we have an automated tool to move to gjs. We’ve almost finished updating all CDCK-owned themes/plugins with that tooling.

So just to confirm (so that I can edit my js/hbs components), hbs components are not supported in the theme skeleton, and is strongly recommended to be moved to gjs?

Hbs files continue to be “supported” (i.e. they’ll work, and we won’t change that without a deprecation cycle) But yes, it’s strongly recommended to use .gjs for new code, and to start migrating existing themes & plugins. The most up-to-date linting config in the skeletons will enforce that recommendation unless you deliberately opt-out of the ‘require-strict-mode’ ember-template-lint rule.

Ah, got it now. Thanks for clarifying!

I believe in any case Glimmer Components can be anywhere between 3 to 5 times faster, so definitely good practice? (so long as you don’t burden them with lots of additional tracking)

Glimmer components are significantly faster than classic components, yup! But the .gjs file format does not necessarily mean it’s a glimmer component. We still have hundreds of classic components in core, which are now all converted to the .gjs file format. (naming is confusing, I know :sweat_smile:) The codemod we’re running only does the file format conversion from js/hbs → .gjs. It doesn’t change the component type - that would be almost impossible to perfectly automate.

[صورة] david: But the .gjs file format does not necessarily mean it’s a glimmer component. Fair enough, but often worth making the effort if you happen to be in the middle of a manual refactor.

[صورة] david: But the .gjs file format does not necessarily mean it’s a glimmer component. OMG. Just when I thought I was starting to understand. [صورة] david: (naming is confusing, I know :sweat_smile:) So it’s not just me! :tada: Does this make it be a glimmer component? And if that’s the case; even if it’s just a template, adding the class makes it run faster than if it’s a .gjs that has just My important words ? export default class MyCoolComponent extends Component {

It’s this: import Component from "@glimmer/component"; (and subsequent conformance to Glimmer norms like getters) [صورة] pfaffman: export default class MyCoolComponent extends Component { this is just a “Native class declaration” I believe.

[صورة] merefield: It’s this: import Component from "@glimmer/component"; Aha! So you’d still need to declare the class to use the imported component part. Thanks very much!

متى يتم تحويل القوالب/الإضافات إلى `.gjs`؟

مطور

merefield (Robert) 13 يونيو 2025، 2:00م 6

أعتقد على أي حال أن مكونات Glimmer يمكن أن تكون أسرع من 3 إلى 5 مرات، لذا فهي بالتأكيد ممارسة جيدة؟

الموضوع		الردود	مرات العرض
Modernizing inline script tags for templates & JS API Development dev-news	46	6154	25 مارس 2026
Templating of my "component" broke. How do I fix it? Development	14	542	17 مارس 2026
Upgrading Discourse to Ember 4 Development ember	19	3500	19 ديسمبر 2024
Overriding plugin javascript in a theme component Development	11	1432	10 أكتوبر 2022
Javascript assets in a theme component Development	15	2533	7 مايو 2021

متى يتم تحويل القوالب/الإضافات إلى `.gjs`؟

الموضوعات ذات الصلة