Application configuration not loaded from add-on dependency tree

[BryanHunt]

Output from ember version --verbose && npm --version && yarn --version:

ember-cli: 3.2.0
http_parser: 2.8.0
node: 10.4.1
v8: 6.7.288.45-node.7
uv: 1.20.3
zlib: 1.2.11
ares: 1.14.0
modules: 64
nghttp2: 1.32.0
napi: 3
openssl: 1.1.0h
icu: 61.1
unicode: 10.0
cldr: 33.0
tz: 2018c
os: darwin x64
6.1.0
bash: yarn: command not found

If you depend on addon a which depends on addon b and addon b contributes to the application configuration, that configuration is not included when the application is built. You must have a direct dependency on addon b for the configuration to be included.

[stefanpenner]

I believe this is by design, as nested addons can dupe

[locks]

Closing due to inactivity and that according to the last comment it is workinig as intended.