Using Ember-CLI with Canary Build



I’ve been trying to include a canary build of Ember so that I can use the query-params-new feature but am struggling to get it working with Ember-CLI. I managed OK using Ember App Kit & following the advice given here…

In fact the last post in this thread suggest a solution that works with Ember-CLI too, but following it I haven’t been able to get a working version.

Could anyone help me understand how they managed to achieve it?

I altered the Brocfile.js to

  var legacyFilesToAppend = [

(changed to index.js from ember.js)

And updated my Bower.json to these dependencies (with a resolution)

"dependencies": {
    "handlebars": "~1.3.0",
    "jquery": "~1.9.1",
    "qunit": "~1.12.0",
    "ember-qunit": "~0.1.5",
    "ember": "",
    "ember-prod": "",
    "ember-data": "~1.0.0-beta.4",
    "ember-resolver": "git://",
    "ic-ajax": "~1.x",
    "loader": "git://"
  "resolutions": {
    "ember": "e-tag:e46b7bbe6"

The version of Ember-CLI I am using is ember-cli@0.0.23 & the version of brocoli is broccoli@0.7.2

The error that I am getting in the browser is

Uncaught TypeError: Cannot read property 'create' of undefined 

Maybe it is a conflict between versions of ember in my dependencies but I am not sure which e-tag to use in this case

Running bower list gives this

├── ember#e-tag:e20b77134
├─┬ ember-data#1.0.0-beta.7
│ └── ember#e-tag:e20b77134 incompatible with >= 1.0.0 (1.6.0-beta.2 available)
├── ember-prod#e-tag:b4693717f
├─┬ ember-qunit#0.1.7
│ ├── ember#e-tag:e20b77134 incompatible with ^1.3.0 (1.6.0-beta.2 available)
│ └─┬ ember-data#1.0.0-beta.7
│   └── ember#e-tag:e20b77134
├─┬ ember-resolver#9805033c17
│ └── ember#e-tag:e20b77134 incompatible with ~> 1.2.0-beta.2 (1.2.2 available, latest is 1.6.0-beta.2)
├── handlebars#1.3.0 (latest is 2.0.0-alpha.2)
├─┬ ic-ajax#1.0.4
│ └── ember#e-tag:e20b77134 incompatible with >=1.2 <2 (1.6.0-beta.2 available)
├── jquery#1.9.1 (latest is 2.1.1-beta1)
├── loader#1.0.0
└── qunit#1.12.0 (latest is 1.14.0)

Thanks for any suggestions.



did you ever figure this out? I am having the same problem



i simply removed "resolutions": { “ember”: “e-tag:e46b7bbe6” }

and it worked great. auto resolved the correct etag.



That’s great - am glad you got it working.

Definitely much simpler now & the docs have just been updated, might be of interest to you…