# Will there be continued support for people that do not want to use Ember-CLI?

**URL:** <https://discuss.emberjs.com/t/will-there-be-continued-support-for-people-that-do-not-want-to-use-ember-cli/7672>\
**Category:** Uncategorized\
**Created:** [March 30, 2015, 6:34pm UTC](https://discuss.emberjs.com/t/will-there-be-continued-support-for-people-that-do-not-want-to-use-ember-cli/7672 "2015-03-30T18:34:22Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![chrisbateman](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/chrisbateman/32/10962_2.png) [@chrisbateman](https://discuss.emberjs.com/u/chrisbateman)\
**Post date:** [June 30, 2015, 9:40pm UTC](https://discuss.emberjs.com/t/will-there-be-continued-support-for-people-that-do-not-want-to-use-ember-cli/7672/20 "2015-06-30T21:40:35Z")

</div>

While I love the idea of Ember-CLI - it’s turning out to be too restrictive.

Ember-CLI [prevents](http://discuss.emberjs.com/t/importing-es6-files-outside-of-app-folder/8150) me from pulling in 3rd-party ES6 modules as well as unnamed AMD modules. I have to roll my own build process in order to do this. But as soon as I want to do that, I lose the benefit of being able to write components in the Ember-CLI style (e.g. I have to import the App into each component).

Wish there was a better alternative for using Ember without the restrictions of the CLI’s build process.

---

_[View the full topic](https://discuss.emberjs.com/t/will-there-be-continued-support-for-people-that-do-not-want-to-use-ember-cli/7672)._