Robbo

What I posted doesn't fully work. It works on fresh loads on any page. But only for the initial engine/app. So if you load an app route it works there...

Engines are just a mess anyway.

I did this change but I still have the issue of going in or out of an engine it doesn't work. What happens is the first loaded part (if app...

I refactored away from engines and life has been easier, so this issue doesn't concern me anymore and I don't suggest anyone use engines at all. I'm gonna unwatch this.

@danidr we have a very big app, and using engines was a very bad decision (by me). Most problems they solve are being solved in other ways with ember octane....

> and as far as I understand, this is the way Ember is going for asynchronous loading of components/routes. Nope or engines would have been improved a lot more by...

Yes and after using it for 11 engines and seeing all the problems in discord over and over I don't think they should be recommended at all. I actually think...

We have to stick to 8.0.1 because `dart-sass` is painfully slow and the `node-sass` never worked in newer versions.

Yeah honestly I'm probably just going to fork this in future based on when it was just `node-sass` instead of trying to support everything.

The fact it never worked when I tried to configure to node last time is why I will be forking it. Node is now a second class citizen here even...