The future of twigs

[xeronimus]

Discuss the future of twigs.

some inputs:

1. Dependency to ng-route : what if someone uses another router library (angular-new-router, ui-router)
2. What about leaving bower and providing twigs as a npm module only
3. What about the future of angular. Should we rewrite twigs for angular2? (in typescript?)

[ChristianKohler]

2: Definitely!

1 & 3 are quiet some work though. Imho, shouldn't be something to do without an actual project using it.

[michaelschnyder]

1: Was never an issue on the projects i worked on, but the current approach seems to be outdated, better option could be: https://github.com/AzureAD/azure-activedirectory-library-for-js/blob/master/lib/adal-angular.js#L194 (maybe this would be compatible with ui-route too?)

2: as long as there are projects depending on the bower-chain, I would suggest not to move away since this would force all hatch-projects to adjust their chain.

3: Not yet

[ChristianKohler]

2: Valid point. But we should support npm in addition to bower then.

[xeronimus]

I agree. We should provide both - for the moment.
see #40