web-sdk-core package

[SamueleA]

Moves various utils, components and types from the connect package to the newly created "commons" package

[cloudflare-workers-and-pages]

Deploying web-sdk-react-example with    Cloudflare Pages

Latest commit:	345b78b
Status:	✅  Deploy successful!
Preview URL:	https://ae88b8e8.web-sdk-react-example.pages.dev
Branch Preview URL:	https://5410-common-package.web-sdk-react-example.pages.dev

View logs

[corbanbrook]

Common package uses README from hooks

[corbanbrook]

As it currently stands i feel like this common package is too broad in scope and it will be growing over time.

It contains react components, contexts, utilities and constants. Some are specific to the connect ecosystem of packages (connect, checkout, wallet-widget), and some could be used more globally in for instance marketplace, builder, or wallet-webapp.

1. I think we need to create a clear demarcation between what is specific to "connect" and what is globally useful.

2. i think we need to break up this package into clear responsibilities of behavior. the web-sdk/hooks package is successfully used across many of our projects now because it aheres to this and is agnostic to connect and low on dependencies.

I would propose that we have separate packages for:

• utilities: globally useful utility functions
• components: globally useful higher level/complex sharable components (that don't belong in design-system)
• connect-core: specific logic which is shared amongst connect based packages (this logic was previously just within the connect package -- maybe it should just go back)