Update version of @wordpress/components

[dechov]

In #571, a severe styling regression from a WP update was dealt with by pinning our version of @wordpress/components to what WooCommerce Admin was using at the time (8.5.0). Now the latter version has been updated as well (see woocommerce/woocommerce-admin#4427).

We should follow suit and update our version (or possibly consider using the external dependency again, despite being demonstrably riskier), which should no longer cause the issue solved in #571, though we'll need to consider newer WCPay releases' compatibility with older WooCommerce Admin versions.

(See also woocommerce/woocommerce-admin#4538.)

[dechov]

The dependency version in woocommerce-admin was now most recently bumped in woocommerce/woocommerce-admin#5293, causing some styling regressions (woocommerce/woocommerce-admin#5345) currently being addressed.

[dechov]

The bundling of @wordpress/components in WC Admin was removed altogether in woocommerce/woocommerce-admin#5753.

[LevinMedia]

@dechov @vbelolapotkov While working on #1378 I noted that the outdated version of @wordpress/components as well as the base components are preventing us from being able to use the correct isSecondary button styles in the disputes section.

I believe @jessepearson may have also encountered this issue while he was working on styling for instant deposits. We should consider re-prioritizing this issue ASAP.

[waclawjacek]

While working on #1378 I noted that the outdated version of @wordpress/components as well as the base components are preventing us from being able to use the correct isSecondary button styles in the disputes section.

I have just encountered this as well while working on #1501.

[vbelolapotkov]

There is a draft PR created but some UI is failing atm due to various deprecations in components props.

[waclawjacek]

@vbelolapotkov Thank you! In the meantime, what is the best course of action to get the current component styles without updating the version numbers? Should I wait for the PR to be merged or backport the button styles?

[vbelolapotkov]

@waclawjacek it depends on the timeline and importance for your PR/feature. If you want it to go live with next release (2.3.0), it's better to copy components/styles you need and create a follow up issue to address once the components package is updated. If it can wait and can be blocked until package is updated, you can build on top of #1536 (I plan to update it soon to make more usable).