Deprecating .js.es6 file extensions in themes and plugins

[david (David Taylor)]

I responded over in the other topic:

Deprecating .hbs file extension in themes and plugins

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 broken and then archiving the GitHub repository. That way, it’s still available for others to fork (assuming the license is permissive enough). We absolutely do care about compatibility & keeping things working. That’s why we have these long deprecation periods with fully automated upgrade paths. We’re always trying to strike the balance between customiza…

but on this point specifically:

@LeoDavidson

There’s no sane reason to stop supporting the old extensions

We have seen significant confusion relating to the .es6 file extensions. This deprecation is motivated by that education/support problem, and not technical constraints.

People end up using .es6 because they copy existing themes/plugins. Then, all sorts of things are broken. In particular: syntax highlighting in editors, intellisense/type-checking, linting, codemods (e.g. the one to fix the .hbs deprecation), etc.

Developer experience is an important part of our platform. Enforcing consistency allows us to improve the education story, improve documentation and improve tooling.