You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen many requests in: "Will you support Vue/Svelte/Ember/<insert your dialect here>" sort of comments in discussions I participated in for linter and formatter support; I thought I extract this here.
While I understand you support popular choices (jsx/styled-components) based on usage to increase adoption and market share, this is perhaps not the most vital choice for the ecosystem in the long run.
Me as an Ember person I did ask for support Ember, too. Apparently within the Ember community there has been a disucssion around this as well and ideally the best wouldn't be any particular tool to do it, but a standard for TC39 - and Ember folks did contribute quite a couple over the years.
So the thing that got me interested in it was the space that JSX, Svelte, Vue, Glimmer, etc. play in—it would be great if there were a natural extension point (even “just” macros! But Rust shows the limits I think) for syntax extension/integration for those kinds of templating languages.
This discussion was converted from issue #17285 on December 23, 2025 02:07.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I've seen many requests in: "Will you support Vue/Svelte/Ember/<insert your dialect here>" sort of comments in discussions I participated in for linter and formatter support; I thought I extract this here.
While I understand you support popular choices (jsx/styled-components) based on usage to increase adoption and market share, this is perhaps not the most vital choice for the ecosystem in the long run.
Me as an Ember person I did ask for support Ember, too. Apparently within the Ember community there has been a disucssion around this as well and ideally the best wouldn't be any particular tool to do it, but a standard for TC39 - and Ember folks did contribute quite a couple over the years.
Yehuda did an early scratch on this, calling it content-tag: https://wycats.github.io/polaris-sketchwork/content-tag.html which actually lead Ember to build content-tag on top of swc (which was the most promising transformer that time): https://github.com/embroider-build/content-tag (this is a tailored impl for Ember to be fair). The most important part here is to take on the idea and that early implementations exist.
Ember would do it's fare and provide it's implementation, and I think other would contribute theirs, too. If there is an API to do so.
There is some good skeets around this, too:
Hope I can spark an interessting discussion here
Beta Was this translation helpful? Give feedback.
All reactions