Cannot read property 'preferNative' of undefined about ember-fetch HOT 7 CLOSED

I'll try to fix this in ember-cli-new-version tomorrow. Thanks for catching this.

from ember-fetch.

This error happens when you have an addon that doesn’t call this._super.included.apply(this, arguments) and depends on ember-fetch. We should absolutely handle this situation better though, and error with an actually helpful message.

from ember-fetch.

@initram were you able to figure out which addon was causing you issues?

from ember-fetch.

I was trying to upgrade ember-cli-new-version. But I have more or less given up on that. The tests kept failing due to some timing issues. But I guess the add-on could still add the initialization.

from ember-fetch.

This is not working for me as well, with an engine.

Setup:

my-app
 - shared-addon
   - ember-fetch
 - my-engine
   - shared-addon
      - ember-fetch

The shared addon does correctly call this._super.included.apply(this, arguments).
However, in the treeForVendor hook,

const preferNative = this.buildConfig.preferNative;

breaks - there is simply no this.buildConfig. Before that, the included hook is called twice.
Not even manually adding ember-fetch to the devDependencies of the engine works.

I will try to investigate how this could be fixed...

from ember-fetch.

Seems this issue shouldn't be closed by #172 as people are still having this #200 although it did solve the engine case.

But seems ember-cli-new-version is the addon that didn't call included hook? @initram can you try patch this addon?

from ember-fetch.

I guess #172 still relies on the included hook to run!

from ember-fetch.