Mark Erikson

@bipin1611 : can you put together a project that actually reproduces this issue? From the screenshot, it looks like you might be putting some non-serializable values into the Redux store,...

Based on that original screenshot, I'm guessing that `exchangeContract: Contract` and `connection: Web3` are actually class instances. Those _should not_ go into the Redux store - only plain JS objects...

FYI, the React team just put up a PR that looks to add what might eventually be "official" support for Suspense triggering: `experimental_use(promise)`. It still throws internally, but only after...

Kevin Ghadyani put up a vid with him talking to Tanner about how React Query does Suspense. Haven't even watched it yet, but throwing it here for reference: https://twitter.com/Sawtaytoes/status/1567606755214983170

In order to fully see what's going on, we really need to see a CodeSandbox or project that shows this happening, so that we can look at the actual behavior...

Yeah, this does look like a real issue, although partly triggered by `persistReducer`. Lenz had a suggestion and I'm going to poke at it to see what happens.

It looks like this isn't specific to Redux-Persist in any way. I can replicate the behavior with: ```ts const store = configureStore({ reducer: combineReducers({ counter: counterReducer, }), middleware: (getDefaultMiddleware) =>...

Short answer is, right now we _don't_ know why it happens :) It seems to be _something_ about the combination of directly calling `combineReducers()` to produce either the root reducer...

Like I said earlier, this seems to happen when you do two things together: - put a function call on the right-hand side of `reducer: ` (in other words, calling...

This _may_ possibly be fixed as a result of the changes in #2001 . Can someone try out the CSB CI build from either #2001 or #2024 , and see...