This is directed at both your comment and the other reply to yours: Angular is a very very opinionated framework. To get as much benefit as possible from it, there's not really an option to make a "universal" framework with Angular as an option. There are few other frameworks that actually use the same workflow as Angular.

I think Ionic has chosen a smart path by building on top of Angular even if you just consider how Angular uses directives. Ionic has built a whole suite of custom mobile specific directives that are approaching native speed.

nope that's the issue when you build frameworks on top of frameworks,instead of making a dependency optional.

Now people dont bother,they can write a script that has nothing to do with angular yet distribute it inside an angular module,instead of making angularjs integration an option.Imagine if code mirror was an angular module, that would be pretty stupid hey? And then everybody move to the next hyped framework ,the project basically dies.