Mark Erikson

@mattoni the normal _RTK Query_ entry point :) `@reduxjs/toolkit/query` or `@reduxjs/toolkit/query/react` .

@kuldeepsinghborana yeah, that's a problem, and that's what i was pointing to in the issue thread. We rely on equality checks, not a single key.

@kuldeepsinghborana no, just converting values into a string is potentially very expensive. Imagine doing a `JSON.stringify()` on the _entire_ Redux state for a large app.

`array.join()` isn't going to help either. `{a: 1}` and `{a: 2}` are both going to stringify to `"[object Object]"`, which is not unique.

That's actually the problem. A selector is, by definition, 100% synchronous and pure (same as a reducer, actually). It gets called synchronously, is expected to return a value immediately, and...

Yeah, unfortunately that won't work with Redux. `useSelector` (and the underlying React `useSyncExternalStore` hook) do expect standard 100% synchronous selector functions. What are you actually trying to retrieve with JSONata?...

Part of the issue is it seems like the entire `state` is needed as an argument. Normally to get that you'd have to use `useSelector(state => state)`, which would force...

The `webpackJsonp` error generally means that Webpack has output multiple chunks, but the one containing the Webpack bootstrapping code wasn't the first chunk loaded into the page. I may glance...

@AndrewCraswell for the record, we've had multiple _minor_ releases of RTK, but no _major_ releases :) we're actually about to publish RTK 2.0 hopefully in the next few weeks, though!

Brian Vaughn joined Replay ( https://replay.io ) a few months ago, and we've been intentionally using pre-alpha/experimental Suspense behavior for data fetching. The pattern Brian introduced is a "Suspense cache",...