Salvatore Ravidà

@escaton yeah you are right. Note that redux-first-history, is even better because batch all history listeners, react-router-dom, and store updates. so again, the MAIN problem of connect-react-router, is that it...

yes. you are missing that history should be in sync with store, always not on mount/unmount. Moreover, CRR will not garantee that state.router.location=== history.location because it duplicated the Source of...

Same here https://github.com/supasate/connected-react-router/issues/311 Try redux-first-history, no location issue.

> I guess we use copy-on-write on macos. So when you change the file, the injected file is not changed. Would a sync command help? > > You may try...

look @ https://github.com/Azure-Samples/SpeechToText-WebSockets-Javascript/pull/52

yeah i suggest to export a reducer-immutable factory ```javascript export function createReducerImmutable(Immutable); ``` so there is NO require("immutable");

yeah all ok!

@drarmstr, any updates? What about the first proposed solution? ```javascript const currentUserInfo = selector({ key: 'CurrentUserInfo', get: async ({get, cleanup}) => { const controller = new AbortController(); const signal =...

Currently, I'm doing this workaround: ```javascript let controller; const currentUserInfo = selector({ key: 'CurrentUserInfo', get: async ({get}) => { if (controller) controller.abort(); controller = new AbortController(); const signal = controller.signal;...

@drarmstr https://github.com/remix-run/history/blob/dev/packages/history/index.ts Maybe recoil URL sync could use well-tested history wrapper: npm "history" package (from the team of react-router)