Bert De Block

@jenweber, I am still able to reproduce this issue.

I also mentioned this a while back in the `ember-data` channel on Discord and this was Chris's response => https://discordapp.com/channels/480462759797063690/486549196837486592/615993948321873930 Might be of use?

I _think_ `@embroider/macros` is responsible for that value and not `ember-get-config` itself.

Looks like this can be closed now?

@lukemelia I think you can also update the PR description to mention that this closes https://github.com/chrislopresto/ember-freestyle/issues/653?

FWIW, we're applying both modifiers to the same element and everything seems to work fine.

Should we also display a deprecation warning at build time when `EXTEND_PROTOTYPES` or `EXTEND_PROTOTYPES.Array` is _not_ set to `false`?

Should we also include something about the `ember-disable-prototype-extensions` addon? Does it remain in the `addon` blueprint output if we set `EXTEND_PROTOTYPES` to `false`?

Sweet! Already opened https://github.com/ember-cli/ember-cli/pull/10017 for Ember CLI.

Are there any docs that show that this should work? I wouldn't expect this to work, but I could be wrong!