# Ember CLI, 2018 Edition

**URL:** <https://discuss.emberjs.com/t/ember-cli-2018-edition/14543>\
**Category:** Ember CLI\
**Created:** [April 16, 2018, 1:04am UTC](https://discuss.emberjs.com/t/ember-cli-2018-edition/14543 "2018-04-16T01:04:13Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![rwjblue](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/rwjblue/32/9411_2.png) [@rwjblue](https://discuss.emberjs.com/u/rwjblue)\
**Post date:** [April 16, 2018, 1:23pm UTC](https://discuss.emberjs.com/t/ember-cli-2018-edition/14543/6 "2018-04-16T13:23:56Z")

</div>

> [@villander](#):
>
> ember-engines will it continue as a plug-in design apart, as well as ember-data? or will it be incorporated into ember-cli?

As discussed in this post [Readers' Questions - "What is the status of ember-engines?"](https://discuss.emberjs.com/t/readers-questions-what-is-the-status-of-ember-engines/14236), the ember-engines addon is really two main things:

1. The build time code needed to enable “lazy engines”
2. The runtime code needed to enable the encapsulation provided by the framework

It is our general plan that the custom build time code that enables “lazy engines” will be moved out of the ember-engines addon and instead be a baked in concept of the ember-cli packaging step. This should not mean conceptual changes for engine authors or users, it should however remove a very large amount of brittle highly coupled code that consistently causes issues for folks. 😺

---

_[View the full topic](https://discuss.emberjs.com/t/ember-cli-2018-edition/14543)._