Ember Template Imports

My argument for <template>: a series in 5 parts.

The Ember and Glimmer community is currently experimenting with designs for components being available in the same file as supporting JavaScript — sometimes described as single-file components” (or SFCs). There are some working implementations in the ember-template-imports repository, and Ember’s community and leadership has already committed to making some move in this space the strict mode templates RFC.

While each of these has its own upsides and downsides, I believe <template> is far and away the best choice, because of its wins for teaching and understanding, scaling, and testing. In this series, I will do my best to present an even-handed analysis that shows how and why I came to that conclusion over the last few years of thinking about it.

It’s important to say before I jump in: these are my opinions. They’re not official LinkedIn positions, and in fact I have a number of colleagues who disagree with me about some of these things! I’m writing this series to persuade any and all members of the Ember community, including other people at LinkedIn.

The planned five posts in this series: