Skip to content
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

Upgrading redux-toolkit from 1.2.5 gave stack trace on saga put() #671

Closed
steinarb opened this issue Jul 28, 2020 · 5 comments
Closed

Upgrading redux-toolkit from 1.2.5 gave stack trace on saga put() #671

steinarb opened this issue Jul 28, 2020 · 5 comments

Comments

@steinarb
Copy link

When I tried upgrading redux-toolkit from 1.2.5 to 1.4.0 today, I got the following stack trace:

Error: [Immer] minified error nr: 19 MapSet. Find the full error at: https://bit.ly/3cXEKWf
    at zt (immer.esm.js:1)
    at en (immer.esm.js:1)
    at yn (immer.esm.js:1)
    at e.t.produce (immer.esm.js:1)
    at redux-toolkit.esm.js:882
    at Array.reduce (<anonymous>)
    at redux-toolkit.esm.js:853
    at redux.js:445
    at p (<anonymous>:1:36402)
    at v (<anonymous>:1:36684)

Immer error 19 referred to in the stack trace, is "plugin not loaded"

The error occurs already at 1.3.0 and downgrading redux-toolkit in package.json doesn't fix the problem.

If I restore the package-lock.json file from before upgrading redux-toolkit from 1.2.5, the problem goes away.

@markerikson
Copy link
Collaborator

Any chance you have multiple versions of Immer in your app after an upgrade?

@steinarb
Copy link
Author

steinarb commented Jul 28, 2020 via email

@markerikson
Copy link
Collaborator

Yeah, I'd filed an issue against CRA a while back that their version of Immer was wayyyy out of date:

facebook/create-react-app#8750

That just got closed and I would assume the fix should be out in the next release (CRA 3.4.2?)

Does use of RTK 1.4 + Immer 7 fix the issue, or is that still happening?

@steinarb
Copy link
Author

steinarb commented Jul 29, 2020 via email

@markerikson
Copy link
Collaborator

I know that Yarn has a resolutions feature as well. Not sure if switching to Yarn would make a difference.

Since there doesn't seem to be anything else actionable on our end, I'll go ahead and close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants