Back in 2020, Discourse switched from the .js.es6 extension to .js. Over the years, the vast majority of themes and plugins have switched to the new extension, which provides much better compatibility with modern JavaScript tooling. We are now formally deprecating the use of .js.es6, and will remov…

Why do you keep doing things like this rather than maintain compatibility? This is just creating more work for no reason. It costs nothing to allow the old and new extensions. They are just filenames. Some of us are trying to do other things, not spend our lives updating Discourse plugins. I’ve a…

.es6 standard is over 10 years old. I think it’s reasonable to expect a deprecation after that length of time?

Is it fair to say your question was already asked and answered here? [image] We're upgrading our icons to Font Awesome 6! megaphoneAnnouncements Sorry for the frustration, we try to make these updates easy and provide months of time to get them done — but ther…

Are there specific plugins you’d like help updating? if they’re open source I’m willing to take a look and open a PR

[image] LeoDavidson: Some of us are trying to do other things, not spend our lives updating Discourse plugins I don’t think this is too much work: [image] david: If you see a deprecation message for .js.es6 files, you simply need to rename them to .js. That’s it. No need to change the co…

[image] awesomerobot: Are there specific plugins you’d like help updating? No, I am going to delete my plugins instead. It’s not that making this particular change and re-testing everything afterwards is difficult. It’s that it’s yet another breaking change made for absolutely no reason, de…

I responded over in the other topic: [image] Deprecating .hbs file extension in themes and plugins Development I’m very sorry to hear that! If you do want to proceed down this path, I’d recommend adding a note to the README & Meta topic, marking it brok…

I understand that this change is frustrating and I would like to find a path to maintaining these plugins if they’re important to the sites using them, specifically so we don’t end up with broken functionality. If there’s any possibility of keeping you involved in that process, that would be prefera…

Any remaining uses of .es6 files will now trigger a warning banner for admins. Depending on real-world-telemetry, we plan to remove support during the 2026.8.0-latest cycle. 2026.7 ESR will be the last release with .es6 support.

Deprecating .js.es6 file extensions in themes and plugins

Development

Canapin (Coin-coin le Canapin) March 31, 2026, 12:55pm 4

Is it fair to say your question was already asked and answered here?

Topic		Replies	Views
Deprecating .hbs file extension in themes and plugins Development dev-news	19	828	July 14, 2026
Case study of an amateur plugin author Development	11	376	May 4, 2026
Discourse markdown extensions not working after latest Discourse upgrade Development	12	763	February 7, 2024
Preparing for Discourse's upgrade to Ember 5 Announcements	53	8063	April 8, 2024
Suggestions for better plugin maintenance Development	15	3078	November 7, 2016

Deprecating .js.es6 file extensions in themes and plugins

Related topics