Feature Request

Is your feature request related to a problem?
Consider this (invalid) code:

12.3e

It throws this error:

Invalid number (1:0)

Describe the solution you'd like

It should throw something like

Missing exponent after 'e' in floating-point number

If you are interested in fixing this bug, you should introduce a new error

An unreviewed change to the automattic/composite-checkout npm package added MainContentUI, CheckoutStepAreaUI, and SubmitButtonWrapperUI to the package's public API.

Those are all CSS-in-JS styled components that were previously implementation details of the package. It totally makes sense to expose them to consumers of the package, but they should be renamed to be more clear (the "UI"

Expected Behavior

We should have some extra basic accessors for the heatmap:

• locale
• loadingState
• isAnimated
• numberFormat?

Difference from Current Behavior

The curr