2.0 Roadmap

Features

• Add modifier managers
• Add experimental helper managers
• Add experimental hostMeta

Cleanup

• Upgrade VM to latest
• Drop support for string resolution of component managers
• README should be updated
• Drop proposal-class-properties babel plugin in favor of preset-env
• Add esm package
• Move root index.html to be in the actual application it’s related to

[pzuraq]

No, the immediate goal is to rebuild @glimmerx on top of Glimmer 2. @glimmerx will have a more opinionated set of defaults, such as default Helper and Modifier implementations, but will otherwise work pretty much the same. It will also ensure it works with both Ember and Glimmer apps but swapping out implementations of things when used in one environment of the other.

See: https://github.com/tomdale/glimmer-lite-donut/

Long term, I’d like to get Ember to a place where it can be rebuilt on this core, but we’re a long ways off from that.

[pzuraq]

Glimmer.js 2 will not support this directly out of the box at first, though it should be possible to add it yourself through a web-component wrapper similar to @glimmer/web-component.

The goal of v2 is to be much more flexible and minimal overall though. There is no more resolution, and no need to create an app instance, so you should be able to use renderComponent multiple times fairly easily. Along with template imports, this should make adopting Glimmer.js incrementally much easier. We are specifically designing this with the ability to adopt incrementally for React/Vue/Svelte users, for instance, if that help.