fix(build): handle module unification addons

[buschtoens]

I wanted to play around with ember-cli-addon-docs in a Module Unification addon, but hit some problems. This in combination with ember-cli/ember-cli#8197 fixes all problems for me.

The ember-fetch upgrade is required for monorepo addons. I'll rebase this PR, when #284 is merged.

This PR here is also lacking tests for MU.

[buschtoens]

So this is working now for classic and MU. However, the story for how to test an addon with classic and MU dummy apps is still shaking out. I guess until then, we can't really write tests for MU.

It would be sweet however, if this PR could be merged nonetheless, as the changes are rather minimal and don't interfere with the classic build pipeline, but would allow early MU adopters to keep experimenting with the mainline release of ember-cli-addon-docs.

[buschtoens]

There is one minor issue I noticed: ember-svg-jar icons don't work, but this is most likely an upstream issue. I'll investigate.

[buschtoens]

The app dir is only partially merged with the MU dummy app, meaning that primarily the docs.api.item route template is not made available out of the box.

The inject-media initializer is executed. The transitions for shift+slash don't seem to work, but they are also broken on master. Try pressing shift+slash here: https://ember-learn.github.io/ember-cli-addon-docs/

[buschtoens]

There is one minor issue I noticed: ember-svg-jar icons don't work, but this is most likely an upstream issue. I'll investigate.

I just noticed that it's fixed now. I guess by ember-cli/ember-resolver#276, but I am not 💯 sure, but also don't wanna waste time finding the exact thing that fixed it. 😂

The app dir is only partially merged with the MU dummy app, meaning that primarily the docs.api.item route template is not made available out of the box.

I've relocated the template in d21fa46, so that it may be imported by the consuming dummy app:

// tests/dummy/src/ui/routes/docs/api/item/template.js

export { default } from 'ember-cli-addon-docs/templates/docs/api/item';

By doing it like this, even the nested components {{api/x-component}} keep working.

[buschtoens]

Maybe we can do some trickery with Route#templateName to avoid the manual re-export.

[samselikoff]

kind of want to wait until MU is finalized to support this? what does everyone think?

Can always come back to it if/when that stuff ever shakes out

[RobbieTheWagner]

I've heard from those on Ember core that MU is going through a rethink and will likely differ from the original vision. With that in mind, I am going to close this for now, and we can revisit when things flesh out more.