Arseni Buinitski

> @nonameolsson no this is not a problem of keycloak-js package, it's a react issue as described above. Should we read this as "we bail out of supporting React 18...

So I first thought of adding this to redux-bundler-react, but it seems like it's either a full-rewrite, or dragging both legacy and current approach at the same time. Not cool...

@SahidMiller might not answer your question if you're not using React, but I'm thinking that in general two approaches are theoretically possible: 1. define and cleanup specific selectors/actions/reactors in runtime...

@HenrikJoreteg actually that would really cover 95% of the cases. My 5% is unfortunately a bit different – I not only have multiple "items", but also multiple "current item group"-s...

Thought on a moment that it still can be covered by this approach – but on another thought – not completely since views would still have to select data relevant...

@HenrikJoreteg sorry – you are absolutely right. Why my brain ejected this from a list of valid approaches is because each leaf component will re-render each time when any item...

> So any components subscribed via `selectActiveWidgets` would re-render if the inputs changed because a new array would be returned. Yep, and that's what I meant originally - I would...

And voilà https://www.npmjs.com/package/redux-bundler-async-resources Hope it'll be useful for someone.

FYI guys, I have extended [redux-bundler-async-resources](https://www.npmjs.com/package/redux-bundler-async-resources) with a lot of new stuff, and re-implemented `createAsyncResourceBundle` there also so interface is the same, and new features are there also. Additionally, I...

It's not possible to say anything unless you describe your problem better. At least, what is missing, and from where. You might want to provide a list of actions you...