Ready for Release
The Ready for Release stage is a phase where the implementation is complete and we're preparing it for an official release. See the list of RFCs ready for release below.
#1099
renderComponent()
renderComponent Summary Add a new API to for rendering components into any DOM element. Motivation Building an app from scratch requires a fair amount of boilerplate today, and renderComponent abstracts a minimal API that would allow easy integration of components in other enviroments, such as Astro, or Vitepress, or Storybook, or runtime demos such as JSBin. This also pairs well with RFC#931: JS Representation of Template Tag, in that both features together give folks enough to use Ember without compilation (compilation still recommended for optimizations, however). Detailed design Users would import renderComponent from @ember/renderer (a pre-existing module)
#1068
tracked-built-ins built-in
Built in tracking utilities for common collections Summary This RFC proposes making the set of collections from tracked-built-ins built in to the framework, in a byte-wise opt-in in a brand new package (@ember/reactive) and able to be used without new. Additionally, these APIs can unblock the implementation of RFC#1000: Make array built-in in strict mode and RFC#999: make hash built in in strict mode (but this is not the main focus of this RFC and only could be an outcome). Motivation tl;dr: performance discoverability aiming towards better cohesion Because tracked-built-