rumbletalk / ngx-rumbletalk Goto Github PK

When www.rumbletalk.com is blocked by a browser or the component fails to load the service, the window is reloaded causing a refresh loop.

I am able to reproduce this in Chrome by blocking www.rumbletalk.com in dev tools.

I believe I tracked the issue down to the line below. When the request to the RumbleTalk service fails, the error handler reloads the window. I don't know what the desired behavior is. Maybe a retry/backoff policy could be implemented and call the component reload function instead of location.reload?

When importing NgxRumbletalkModule into a lazy loaded module, I receive the following error:

ERROR Error: Uncaught (in promise): Error: BrowserModule has already been loaded. If you need access to common directives such as NgIf and NgFor from a lazy loaded module, import CommonModule instead.

Replacing BrowserModule with CommonModule in the following file resolves the error and the app is able to load.