Open LuizAsFight opened 1 month ago
Should we consider the update from the old UI library to the new one before/after this migration?
good point @luizstacio we can split the work:
fuels-npm-packs
, which doesn't depend on the old UIfuels-wallet
, and migrate to the new fuels/ui
together. by doing this we 100% get rid of the legacy UI
we currently have many repos which makes hard to be updating and changing versions across them, bringing lots of overhead work in our development cycle
current repos are:
fuels-wallet
fuels-npm-packs
fuel-connectors
fuel-explorer
this issues proposes to unite following repos, migrating them to live inside
fuel-explorer
in the format of new packagesafter this change, frontend stack will have only this repos:
benefits:
disadvantage:
PS:
npm
packages that will not be maintained anymore