[no-Jira] Deduplicate frontend yarn packages

[canac]

Description

I hope this will decrease bundle sizes because emotion packages won't be included in the bundle multiple times anymore.

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels. (Add the label "On Staging" to get the branch automatically merged into staging.)
• I have requested a review from another person on the project

[github-actions]

Preview branch generated at https://yarn-dedupe.d3dytjb8adxkk5.amplifyapp.com

[github-actions]

Bundle sizes [mpdx-react]

Compared against 5f6646c

No significant changes found

[canac]

@dr-bizz I guess this doesn't actually change the bundle sizes. I can close this if you think it's not worth doing.

[dr-bizz]

How did you know it was duplicated, and then how did you remove it. Is there a yarn command?

[canac]

How did you know it was duplicated, and then how did you remove it. Is there a yarn command?

@dr-bizz yarn dedupe --check will show you packages that can be deduplicated, and yarn dedupe will do the deduplication. For this PR I ran yarn dedupe '@emotion/*' '@mui/*' '@popper/*' to only deduplicate packages that look like they are used on the frontend. Most of the duplicates appear to come from dev dependencies and aren't included in the client bundle.

[canac]

@dr-bizz Did you have any more thoughts on this? The change in bundle size isn't enough to trigger the bundle analyzer comment, but it goes down by 235 bytes for _app.js and about 300 additional bytes for the flows/setup and fixCommittmentInfo pages.

[dr-bizz]

You are fine to merge this, even if it doesn't change that much