-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with Devtools and StoreRouter #61
Comments
#60 is not related anymore. I refreshed to the newest version of the nightlies and I get nearly the same as you. The error can be caused by 'window.webkitStorageInfo' which is deprecated in chrome. Sometimes it stats to eat up memory and freeze the browser. The same happens in Firefox. |
The problem is with the redux devtools. It causes the error. If I disable it. The website works. |
I found this. It seems to happen only with lazy loaded routes. |
In my case it was because of an undefined value in the routerLink directive. The value was not loaded yet and the error occurred. I changed the link to a function that checks whether the value is set and then navigates the route. So, maybe that will help someone else ... it could be because you are navigating with an undefined value (like ID) in routerLink (or similar). |
@brandonroberts when using the shim
we get the error:
This happens just when using Maybe related to zalmoxisus/redux-devtools-extension#315 |
Can confirm it is happend with lazy loading module when
|
Any idea how to fix this? For me this still happens so I cannot use the |
I just spend some time on debugging the issue. So the thing is it is polyfils issue. You have to disable/comment That the piece of code from the polyfil which is causing the problem:
I just reported the issue here zloirock/core-js#347 |
My browser freezes and eats up memory when I add StoreRouter 🤔 But |
@GuskiS I "fixed" this by removing the router store ... that caused a lot of issues. But maybe you won#t be able to, so simply. |
Well, I was just trying to add it, so no harm for me to not use it, but I would rather have it than not have it. |
I was getting this error as well. I was refactoring my app and determined that the issue was because I had included |
Leaving this here for reference to handle router store issue https://github.com/ngrx/platform/blob/v4.1.1/docs/router-store/api.md#custom-router-state-serializer |
So the fix is to create our own, custom serializer? |
@GuskiS for now, yes. There is an Angular PR to make the router state serializable, but no timeline on when that will land. |
I have encountered this with an Ionic Framework (v3.9) app, even though I am not using Has anyone else hit this in an Ionic project? Update: Figured out that the error was due to a store property that couldn't be serialized, possibly due to circular references. I didn't have luck with creating a custom serializer - I ended up refactoring code to make this object available in a provider instead of a store. |
Bug, feature request, or proposal:
BUG
What is the expected behavior?
No errors
What is the current behavior?
When using StoreDevTools and the RouterConnectionModule together I also am getting some issues, which are the same as in the 2.x branch (see ngrx/store-devtools#61).
The error is the same:
What are the steps to reproduce?
It happens after a dispatch action and then navigating away from that page. The FIRST click creates the above error. The second click works again, after which the error does not occur again.
Refreshing the page and following the same steps creates the same issue.
If I take out the RouterConnectionModule the error DOES NOT occur.
The setup in AppModule is the following:
Which versions of Angular, NGRX, OS, TypeScript, CLI, browsers are affected?
Is there anything else we should know?
May relate to #60
The text was updated successfully, but these errors were encountered: