# Ember-CLI migration questions

**URL:** <https://discuss.emberjs.com/t/ember-cli-migration-questions/6966>\
**Category:** Ember CLI\
**Created:** [December 21, 2014, 3:43pm UTC](https://discuss.emberjs.com/t/ember-cli-migration-questions/6966 "2014-12-21T15:43:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gordon\_kristan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/gordon_kristan/32/14862_2.png) [@gordon\_kristan](https://discuss.emberjs.com/u/gordon_kristan)\
**Post date:** [December 21, 2014, 3:43pm UTC](https://discuss.emberjs.com/t/ember-cli-migration-questions/6966/1 "2014-12-21T15:43:23Z")

</div>

I’ve been using a custom build/module system for the better part of a year now (since just before Ember-CLI got popular). But now that Ember 2.0 is looking to move to Ember-CLI and Ember-CLI is a bit more stable, I’m looking to migrate. I’m doing a test run with our code right now and I have a few questions that hopefully somebody can help with:

1. Our company has a few dependencies installed via Bower that don’t contain `bower.json` files. Some of them are ZIP files that get extracted, some are GitHub Gists that contain the files we want. When adding these dependencies to `bower.json` with Ember-CLI, `ember server` doesn’t run because it doesn’t think those dependencies are installed. Is there some way to manually configure how Ember-CLI handles Bower dependencies? It seems unnecessary to put these in the `vendor` folder and check them in to Git when they’re available online.

2. All of the dependencies and vendor scripts get compiled into a single `vendor.js` file and this is **awful** for debugging. I’m not even done including dependencies and my `vendor.js` file is over 80,000 lines. Trying to open and debug that in Chrome is a huge pain. Is there a way to keep the dependencies as separate files in development mode?

3. Is there a way to get more fine grained with Ember imports like in the Ember source code? For instance, I have this code currently:

```nohighlight
import Ember from 'ember';

export default Ember.Route.extend({
	
});

```

But I would like to be able to do something like this:

```nohighlight
import Route from 'ember-routing/system/route';

export default Route.extend({
	
});

```

I think it allows one to more easily assess what features a particular module is using, not only from manual inspection but from searching with my IDE as well.