Expose application tokens via ngProbe for chrome extensions, ...

[tbosch]

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.

[tbosch]

This is blocking batarangle

[tbosch]

with #7161 you can:

var ngRootEl = window.getAllAngularRootElements()[0];
var rootNgProbe = window.ng.probe(ngRootEl);
var appRef = rootNgProbe.inject(window.ng.probe.coreTokens.ApplicationRef);
appRef.tick();

var ngZone = rootNgProbe.inject(window.ng.probe.coreTokens.NgZone);
ngZone.onEventDone.subscribe(function() { console.log('Angular did some work'); });

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}