📦 Patch Redux + use RTK alpha for full ESM support

[QuintonC]

ℹ️ What is the context for these changes?

Addresses an issue with Redux Toolkit and ESM support. When attempting to use the package in Next.js an error would be present stating addListener was not exported. This was primarily due to the lack of support for ESM usage in Redux Toolkit, which version 2 aims to resolve.

This makes use of an alpha package and a patch in order to remove an EmptyObject type from the Redux CombinedState type.

After chatting with some of the team from Redux, it appears the only "downside" to removing EmptyObject from the CombinedState type is that we must ensure that our initialState passed to combineReducers has all keys defined (which we already did anyway).

🕹️ Demonstration

State (w/ Demo)	Image
Before
After

🎩 How can this be tophatted?

There are demo links on the demonstration :)

✅ Checklist

• Tested on mobile N/A
• Tested on multiple browsers N/A
• Tested for accessibility N/A
• Includes unit tests N/A
• Updated relevant documentation for the changes (if necessary) N/A

[QuintonC]

/snapit

[github-actions]

🫰✨ Thanks @QuintonC! Your snapshots have been published to npm.

Test the snapshots by updating your package.json with the newly published versions:

yarn add @shopify/[email protected]

yarn add @shopify/[email protected]

yarn add @shopify/[email protected]

[jamiely]

We paired on this and it seems fine, but how will we maintain this? Does it require documentation? Should there be some issue to look into this again a couple months from now?

Also, the codesandbox links open and I understand they are for next, but should we have some place to tophat our regular installation (non-next)?

Edit: After thinking about this, I figured I can just clone and test as usual.

[jamiely]

Tophatted on metamask desktop 👍

[caropinzonsilva]

We paired on this and it seems fine, but how will we maintain this? Does it require documentation? Should there be some issue to look into this again a couple months from now?

Plus one on this. Do we know if it is going to get patched to the actual package in the future?

[QuintonC]

We paired on this and it seems fine, but how will we maintain this? Does it require documentation? Should there be some issue to look into this again a couple months from now?

Plus one on this. Do we know if it is going to get patched to the actual package in the future?

@jamiely @caropinzonsilva great questions. From my understanding, this is actively being worked on by the folks over at Redux. The patch we're using here should be resolved when this PR is merged. If that PR doesn't get merged there's not any concern either as it's on the Redux team's active roadmap to remove the EmptyObject type intersection from my conversations with that team in the Reactiflux Discord.

[caropinzonsilva]

Sound good! Can we create an issue for it? So that we don't totally forget about it :P

[QuintonC]

Sound good! Can we create an issue for it? So that we don't totally forget about it :P

Yeah, of course! I'll get one created momentarily 🙌

Issue created! #46