Switch from @kyper/mui to @mxenabled/mxui

[mwclemy]

Since @kyper/mui is no longer maintained, this change updates imports to @mxenabled/mxui, which enables us to use newly added components going forward. Everything should continue to work as expected.

Changes

• Replaced @kyper/mui imports with @mxenabled/mxui
• Applied MXUI theming override pattern by passing a single primary color and letting MXUI generate the rest of the palette

Testing Instructions

• Go through all Connect flows and confirm everything still appears the same
• Run integrations and E2E tests

[codingLogan]

This is a pretty big change, in terms of how many files and components could be affected.

I'll take some time to load this up, run e2e tests, and manually run some other views and tests.

[mwclemy]

This is a pretty big change, in terms of how many files and components could be affected.

I'll take some time to load this up, run e2e tests, and manually run some other views and tests.

Based on the conversation with the MXUI team, this migration may affect client theme overrides. I'm holding off on the review for now to make sure those overrides are properly accounted for first.

[ash-wright123]

Pulling this down now to start testing.

[ash-wright123]

The logos on the verification account list are off.

[ash-wright123]

The bottom line on the favorites screen is a bit too high and cutting into the list.

[ash-wright123]

The asterisk for the required field is on a new line now on the delete member survey and it should be on the same line as the description.

[ash-wright123]

In the entire disclosure the arrows are off not just on this screen but in the subsequent screens as well.

[codingLogan]

Given the above uncaught issues, we may need to revisit the approach to migrating to MUI/MXUI...

I recommend that we slow the migration down. Ideally, we need to make sure we migrate correctly with one flow or set of pages at a time. With 77 files changed, there's no way to actually know what issues we're going to run into unless we manually test every view we have.

It's a hard pill to swallow for the author and reviewer when there are so many changes 😢 , and it's especially painful when revisions are needed to fix any found issues.

Now, we don't have to break it up, but it would make it easier and more accurate for everyone if we do, especially if we're trying to be accurate to Figma's designs.

[mwclemy]

Given the above uncaught issues, we may need to revisit the approach to migrating to MUI/MXUI...

I recommend that we slow the migration down. Ideally, we need to make sure we migrate correctly with one flow or set of pages at a time. With 77 files changed, there's no way to actually know what issues we're going to run into unless we manually test every view we have.

It's a hard pill to swallow for the author and reviewer when there are so many changes 😢 , and it's especially painful when revisions are needed to fix any found issues.

Now, we don't have to break it up, but it would make it easier and more accurate for everyone if we do, especially if we're trying to be accurate to Figma's designs.

I’m not opposed to breaking up the PR if needed, but I think in this case most of the changes are simply import updates (mainly Text, some icons, and a few MUI overrides that are specific to our project). The only notable issue I’ve run into so far is the misaligned logos on the verification account list that Ashley caught, which turned out to be related to CssBaseline introducing margin conflicts with older Kyper styles.

Given that, I see this migration as fairly low risk. It’s been stalled for a while already as we’ve tried to ensure everything works correctly, and at this point it’s starting to block both our work and UCW’s. My sense is that keeping it as a single PR will help us move forward faster while still being manageable to review, since the bulk of changes are straightforward.

[mwclemy]

The misaligned styles have been fixed. It’s ready for another look whenever someone has a chance. @ash-wright123

[Jameson13B]

Massive MR but in my flows and tests things seem to be working great. Awesome job getting Kyper out.

[github-actions]

🎉 This PR is included in version 2.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀