Chrome extensions don't know which module loader is being used in the application under test. They can get hold of the injector at elements via ngProbe and DebugNode, but they can't access things like ApplicationRef or NgZone as they don't have access to their types to pass into the DebugNode.inject(<token>.
Solution: Provide all exports of angular2/core via a property on ngProbe.ngCore.
Chrome extensions don't know which module loader is being used in the application under test. They can get hold of the injector at elements via
ngProbeandDebugNode, but they can't access things likeApplicationReforNgZoneas they don't have access to their types to pass into theDebugNode.inject(<token>.Solution: Provide all exports of
angular2/corevia a property onngProbe.ngCore.