If the flow plugin runs before the class properties one (or if the class properties plugin isn't used), we remove uninitialize class fields:

class Foo { x: string }

currently becomes

class Foo {}

while it should be

class Foo { x }

If someone still wants the old behavior, they can either use flow comments (as [offically recommended](https://github.c

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