# Deprecating .js.es6 file extensions in themes and plugins

**URL:** https://meta.discourse.org/t/deprecating-js-es6-file-extensions-in-themes-and-plugins/398894
**Category:** Development
**Tags:** dev-news
**Created:** [20 maart 2026 om 16:03 UTC](https://meta.discourse.org/t/deprecating-js-es6-file-extensions-in-themes-and-plugins/398894 "2026-03-20T16:03:38Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![LeoDavidson](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leodavidson/32/119574_2.png) [@LeoDavidson](https://meta.discourse.org/u/LeoDavidson)
#### Post date: [7 april 2026 om 12:04 UTC](https://meta.discourse.org/t/deprecating-js-es6-file-extensions-in-themes-and-plugins/398894/7 "2026-04-07T12:04:31Z")

</div>

> [@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_, demonstrating that the Discourse team couldn’t care less about backward compatibility and breaking people’s forms and code.

The file extensions I used in this project were the ones the Discourse team told me to use at the time the plugin was written. There’s no sane reason to stop supporting the old extensions, but you’re doing it anyway because the team values making things slightly tidier on their side of things than keeping things _working_.

The team have messed up priorities and I’ve had enough of it.

---

_[View the full topic](https://meta.discourse.org/t/deprecating-js-es6-file-extensions-in-themes-and-plugins/398894)._