Edward Faulkner

Also, I think having an **unused** copy of `@babel/core` in the app is bad, and so to address that we should change ember-cli-babel so it moves `@babel/core` from `dependencies` to...

This recursive peer dependencies situation actually makes sense when you consider that it requires each addon to document what range of babel it works under, and those requirements necessarily recurse...

We're not free to pick and choose here, babel has decided that plugins are peerDeps of `@babel/core` so there's really only one correct way to do that and it's the...

Ask yourself: why do babel plugins have a peerDep on `@babel/core` in the first place? If they need to access something from `@babel/core` they can just have their own dependency...

The main one to start with is ember-cli-babel.

This is a good change, without it people cannot reliably adopt the new pattern that is documented for 3.0 (importing directly from miragejs).

It's a good question. Certainly each engine needs to be able to interact with the routing service in the same way any application does (it should not require refactoring those...

I spent some time trying to test embroider under PNP and it seems to be blocked on issues within ember-cli itself. For example, `ember-cli/lib/broccoli/ember-app.js` is trying to load jquery from...

@bartocc I had to make a shim program that I could launch with node like: ```js // launch.js require('ember-cli/bin/ember') ``` Then something like: ```sh node --inspect-brk --require /Path/To/Your/.pnp.js ./launch.js ```

That makes sense. So I think in detail it would be: 1. If the user provided their own broccoli tree as `app.trees.styles`, we just use that and there's nothing else...