tamp bundle sizes back down in wake of the crypto-js@4 upgrade

[svidgen]

Is this related to a new or existing framework?

CRA, Next, Webpack4

Is this related to a new or existing API?

Authentication

Is this related to another service?

No response

Describe the feature you'd like to request

Some of the bundle sizes have grown as a result of upgrading to crypto-js@4 (#8273), an upgrade driven by security concerns. To prevent other bundle size spikes going unnoticed, bundlewatch config is being updated: #8321.

Describe the solution you'd like

Investigate ways to get the bloat out of the bundle. Consider alternatives to crypto-js. Ideally, bring bundle sizes back down to:

cra → 90kb
next → 40kb

Describe alternatives you've considered

There are no clever alternatives that I'm aware of, other than acceptance that my bundle sizes are unnecessarily huge now :(

Additional context

No response

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.