# Named imports from Ember and Ember-Data in Ember-CLI

**URL:** <https://discuss.emberjs.com/t/named-imports-from-ember-and-ember-data-in-ember-cli/6326>\
**Category:** Ember CLI\
**Created:** [September 23, 2014, 2:06pm UTC](https://discuss.emberjs.com/t/named-imports-from-ember-and-ember-data-in-ember-cli/6326 "2014-09-23T14:06:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![macu](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/macu/32/5402_2.png) [@macu](https://discuss.emberjs.com/u/macu)\
**Post date:** [September 23, 2014, 2:06pm UTC](https://discuss.emberjs.com/t/named-imports-from-ember-and-ember-data-in-ember-cli/6326/1 "2014-09-23T14:06:47Z")

</div>

I am migrating a project from using Gulp/RequireJS to Ember-CLI. Here is a sample of the RequireJS configuration the project was using:

```nohighlight
require.config({
  shim: {
    'ember': {
      deps: ['jquery', 'handlebars'],
      exports: 'Ember',
      init: function() {
        // Support ES6 default import.
        return this.Ember['default'] = this.Ember;
      }
    }		
  }
});

```

This would support three import styles:

```nohighlight
import Ember from 'ember';
module Ember from 'ember';
import { Controller, RSVP, Logging, run } from 'ember';

```

The third style is used in hundreds of source files.

Would it be possible to configure the Ember-CLI resolver to allow the third style of import from ‘ember’ and ‘ember-data’? Currently it is only possible to `import Ember from 'ember';` and `import DS from 'ember-data';` because the import only has a `default` key. This would be a good feature for teams that prefer using named imports.