I don’t know Angular 2 (and I only know enough Angular 1 to have written our old samples/angular.html sample). However it is apparent that all of the calls are due to Angular’s change detection – trying to find state that has changed and updating accordingly. In this case it seems that there is some internal GoJS state changing that Angular is detecting.
I believe one possibility is to declare that Angular should not do its default change detection:
But there’s probably a way to make that more specific. You might want to create a separate component just for the Diagram, so that this change detection strategy doesn’t apply to the rest of your HTML within this “my-app” component.
And I’m sure someone who actually knows Angular 2 can provide an even better way to avoid all of that automatic change detection.