Evaluate if we can move away completely from wordpress/components

[senadir]

This is the most extreme one, currently we use many wordpress/components here and there, the complete list, if we can move away from most of them, we can gain SIGFNIFCANT bundle gains, and reduce the complexity of our bundle and problems we get from supporting many versions, as long as we support 5.3 we will always be a release or two away from fixes and new things, this is 6 months worth of changes, we're not using anything advanced tbh most of those are basic divs .
The idea of sharing code between projects is wonderful in theory, but the fact that you have to support multiple versions and perform extreme gymnastics and still have to use a 6 months old version is not very compelling, if we ever reach a point of version parity with GB or WordPress (which I don'th think is possible) we might find some use in it, currently 4 of those components cause problems:

• checkbox with IDs issue (that Albert is working on CheckboxControl: stop using Gutenberg's CheckboxControl to avoid duplicated ID's #2097).
• PanelBody and PanelRow extra weight Evaluate if we can move away from PanelBody and PanelRow #2142.
• Card extra weight Evaluate if we can move away from Card component #2141.

Both are blocked by the fact that we can update or not (#2140)

The need to update will also be blocking this (or reverse) since if we can update (lesser evil) we solve some issue.

The best solution is to completely move away, which should be investigated before the rest.

the components we use:

assets/js/base/components/cart-checkout/button/index.js:
  4: import { Button as WPButton } from 'wordpress-components';

assets/js/base/components/cart-checkout/shipping-rates-control/package-options.js:
  8: import { Notice } from 'wordpress-components';

assets/js/base/components/cart-checkout/shipping-rates-control/package.js:
  9: import { PanelBody, PanelRow } from 'wordpress-components';

assets/js/base/components/checkbox-control/index.js:
  4: import { CheckboxControl as WPCheckboxControl } from 'wordpress-components';

assets/js/base/components/loading-mask/index.js:
  7: import { Spinner } from 'wordpress-components';

assets/js/base/components/payment-methods/no-payment-methods/index.js:
  5: import { Placeholder } from 'wordpress-components';

assets/js/base/components/select/index.js:
  6: import { CustomSelectControl } from 'wordpress-components';

assets/js/base/components/store-notices-container/snackbar-notices.js:
  4: import { SnackbarList } from 'wordpress-components';

assets/js/blocks/cart-checkout/cart/full-cart/index.js:
  21: import { Card } from 'wordpress-components';

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Remove the stale label or post a comment, otherwise it will be closed in 10 days.

[github-actions]

This issue has been marked as stale because it has not seen any activity within the past 60 days. Our team uses this tool to help surface issues for review. If you are the author of the issue there's no need to comment as it will be looked at.

Internal: After 10 days with no activity this issue will be automatically be closed.

[senadir]

We moved away from this solution for some time now when we updated our components version.