In the latest version of Discourse, using .hbs files in themes and plugins is deprecated. Support for this file format will be removed after the next ESR release. Handlebars templates should be replaced with the more modern .gjs format, which provides a much better development experience, and will enable large performance improvements in future versions of Discourse. For simple cases, share your code with https://ask.discourse.com/, and ask it to rewrite in the .gjs format. For more complex cases, updates can be automated using using this codemod: [画像] Automatically updating themes and plugins to .gjs file format Development In the latest version of Discourse’s standard linting config, we’ve enabled the require-strict-mode ember-template-lint rule. This will raise a linting error for any .hbs files. To resolve the warnings, you should convert all your component, route, and connector templates to .gjs files. To make this easy, we’ve built the discourse-gjs-codemod, which builds on top of Ember’s @embroider/template-tag-codemod. To use the codemod, first ensure that your linting dependencies are up-to-date by copyin…

[画像] david: after the next ESR release Do I understand correctly that 2026.7 will still support hbs files and 2027.1 will be the first ESR release that doesn’t?

Yes, exactly. It’s most likely that we will drop support in 2026.8.0-latest. But it’s possible it could be later, depending on real-world data and community feedback.

Just came across this one, guess it needs to be updated [画像]Modernizing inline script tags for templates & JS API Templates introduced using this method should be moved to dedicated .hbs files, or refactored into gjs files. To keep as HBS, connector templates can be placed in: {theme}/javascripts/discourse/connectors/{outlet-name}/{connector-name}.hbs and component templates can be placed in: {theme}/javascripts/discourse/components/{component-name}.hbs

Thanks! Hopefully most people have already taken care of those, since they have been deprecated with an admin banner for almost a year. Just in case, I added this note: [画像]Modernizing inline script tags for templates & JS API :warning: Since March 2026, .hbs files are also deprecated. After making this conversion, move on to the instructions in Deprecating .hbs file extension in themes and plugins

Pour ma part, j ai essayé pour mon ptit plugin perso et j ai réussi avec l aide de ask Discourse qui a fusionné mes fichiers hbs et js en un fichier gjs. Je conseil grandement l utilisation de ask Discourse pour résoudre ce problème pour ceux comme moi ont d des difficultés de développement :rofl:

That’s great! I’ve added a note about ask.discourse.com in the OP as well. If you only have a few files, it can work very well :100:

I have no idea what a .gjs file is, nor time to learn about them and re-write multiple plugins. This is ridiculous. What is the point of even having a plugin API if it is as fragile as the one in Discourse? Maintaining plugins for this forum software has been nothing but trouble.

It’s far from ridiculous. If you don’t have the budget or bandwidth to manage customisations then I would urge you to simplify your setup. It’s imho the (reasonable) price you pay for remaining on a cutting edge high velocity platform that keeps on innovating, improving performance, deploys frequent security patches and keeps up with evolving standards. The Discourse team appears to put a lot of effort into ensuring there are deprecation warning messages well in advance of losing function. Would you rather be stuck on an insecure platform with fewer features? Think of the value you get from the well maintained core that you can download for free?

[画像] LeoDavidson: I have no idea what a .gjs file is, nor time to learn about them and re-write multiple plugins You don’t even have to know what a .gjs file is: Automatically updating themes and plugins to .gjs file format

cela n’a pas marché pour mon petit plugin. :sob: Mais avec l’aide de ask.discourse.com , il a lu mon code et m’a converti mon fichier hbs et js en .gjs donc il ne faut pas hésiter si la première méthode ne fonctionne pas

テーマとプラグインにおける.hbs ファイル拡張子の非推奨化

開発

david (David Taylor) 2026 年 3 月 25 日午後 12:19 7

それは素晴らしいです！OPにもask.discourse.comに関する注記を追加しました。ファイルが数個しかない場合は、非常にうまく機能しますよ

トピック		返信	表示
Case study of an amateur plugin author Development	11	686	2026 年 5 月 4 日
Deprecating .js.es6 file extensions in themes and plugins Development dev-news	9	866	2026 年 7 月 14 日
Modernizing inline script tags for templates & JS API Development dev-news	46	6268	2026 年 3 月 25 日
Preparing for Discourse's upgrade to Ember 5 Announcements	53	8914	2024 年 4 月 8 日
Upgrading Discourse to Ember 4 Development ember	19	3529	2024 年 12 月 19 日

テーマとプラグインにおける.hbs ファイル拡張子の非推奨化

関連トピック