Angular 2.0.0-rc.1 no longer exports BrowserDomAdapter

[rn1d]

Prior to Angular 2.0.0-rc.0, it was possible to import and use BrowserDomAdapter in the application. Seems like it is no longer exported from @angular/platform-browser. Is this intentional or a bug?

Originally, I asked the question on StackOverflow: http://stackoverflow.com/questions/37068937/accessing-dom-in-angular-2-rc

Is there an API that should be used instead?

[mprobst]

Could you just implement DomAdapter?

[Cowlephant]

Dealing with this issue myself. Where is DomAdapter? I've used BrowserDomAdapter a lot because everything said to use it.

[mprobst]

I spoke to soon, DomAdapter isn't exported either.

The disappearing BrowserDomAdapter is an accidental side effect of @IgorMinar's big package refactoring in a66cdb4. That also seems to have disabled the former API test.

[naveedahmed1]

Martin can you please also check AnimationBuilder, it seems this has also been removed. The below line doesn't work anymore:

import {AnimationBuilder} from 'angular2/src/animate/animation_builder';

[mprobst]

@naveedahmed1 'angular2/src/animate/... should be @angular/platform-browser, but I think the export for AnimationBuilder also got accidentally removed.

[naveedahmed1]

Ok, thank you Martin for the information. It seems currently the beta 17 is more stable than RC1.

[Falx]

Are there any reasons to use BrowserDomAdapter in favor for plain js document ?

[mprobst]

@Falx document works as long as you don't render on the server side. But beware of XSS bugs!

[Falx]

@mprobst Ok thanks, because I removed BrowserDomAdapter when I saw it wasn't exported anymore, in favor of document. But I seems it would be better to add it in again, once fixed.

[Cowlephant]

So is using document fine then? I thought we encouraged to not use it in favor of browserdomadapter

[IgorMinar]

DomAdapter, BrowserDomAdapter and Parse5DomAdapter are just implementation details and should not be used as public apis. This is why you can't find it any more in the public api surface.

If you need access to document then you can inject it via the DOCUMENT token. If you don't care about DI then you can access it directly. If you are using web workers and want to render stuff into dom then you should be implementing a custom renderer.