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 th

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.