amCalendar causes protractor to timeout on waiting async Angular

Description of the Issue and Steps to Reproduce:

Did you search for duplicate issue? [Yes]

Please describe the issue and steps to reproduce, preferably with a code sample / plunker:

e2e protractor tests fail after amCalendar pipe is used:

Timed out waiting for asynchronous Angular tasks to finish after 50 seconds.

Ensure your issue is isolated to angular2-moment. Issues involving third party tools will be closed unless submitted by the tool’s author/maintainer.

Environment:

Please answer the following questions:

• Angular version: 4.0.0-rc.2
• TypeScript version: 2.2.1
• moment version: 1.1.0
• Are you using moment-timezone: no
• Are you using the angular-cli: yes
• Using Rollup/Webpack/System.js/Ionic/similar?

[romanovma]

Yes, it helps 😃 Unfortunately I don’t know how to pass ngZone to the static method(which initTimer is) so I converted it to non-static and removed refs as we don’t need then anymore in this case. That can cause performance issues but I don’t have good environment to test near at hand. May you have some? Please review and let me know if it is OK to leave initTimer as non-static or may be you know a good way how to pass ngZone to static methods. Thanks for helping.

[urish]

True, we don’t need it - I left you a comment. We can entirely skip the ChangeDetectorRef parameter to initTimer, also, we can remove the runOutsideAngular call from the constructor (but keep that part that’s inside - the subscribe call)