Adding BrowserAnimationsModule and NoopAnimationsModule causes webpack HMR to duplicate the app element on update

[JimLynn]

Using exactly the same code as in the angular-animations-example branch, any changes to the app that invokes the webpack hot module replacement results in the previous app element being left behind underneath the newlay added app element. A browser refresh is necessary to get rid of it and test as normal.

This seems to be provoked merely by importing the two AnimationsModules into the browser and server app modules.

Here's my demo of the problem.

JimLynn/AngularCoreWithAnimation@356be71

[SteveSandersonMS]

Thanks for reporting this.

Closing as duplicate of aspnet/JavaScriptServices#1231, as I am certain that fixing that issue will also resolve this one.