next steps (migrating other components and hooks)

[technophile-04]

Description:

Things done till now:

We have two packages inside the packages dir packages/hooks and packages/components which we are planning to release as two separate packages to npm @scaffold-ui/hooks and @scaffold-ui/components. I already got namespace for scaffold-ui on npm 🙌

Check out the README.MD for local setup and testing. We can use example dir present in this repo to test how the components and hooks work and we could test it finally with SE-2 so that orchestrate how a third-party application will consume these hooks and components.

Next steps:

Start with migrating the hooks and components. Some notes on migration flow:

1. For components, we should use plain tailwind classes instead of daisyUI
2. When creating a PR, let's include both components and hooks related to that component in same PR 🙌

List of hooks and components to migrate:

components:

• Address

Probably not required:
5. InputBase
6. IntegerInput
7. BlockierAvatar

hooks:

Hooks required for Balance components:

• useBalance (name conflict with wagmi but probably it's fine and we could export nativeCurrency balance, current price etc. Similar to useAddress)
• expose useWatchBalance hook as well.

Hook required for AddressInput component:

• useAddressInput

Hook required for EtherInput:

• useEtherInput

We might also find new hooks which can be helpful for others, like useWatchBalance lets discuss that on PR 🙌