It is confusing that the version of fcl-js drifts away from fcl-core, as the latter is simply an implementation detail and should not be interfaced with directly by users. Version bumps in fcl-js should be aligned with those in fcl-core (i.e. a minor change in fcl-core is ultimately a minor change in fcl-js)
We can consider pinning fcl-react-native as well (even though this library is currently unusable, so it's somewhat questionable whether this should be published at all).
Suggest A Solution
No response
What are you currently working on that this is blocking?
Issue to be solved
It is confusing that the version of fcl-js drifts away from fcl-core, as the latter is simply an implementation detail and should not be interfaced with directly by users. Version bumps in fcl-js should be aligned with those in fcl-core (i.e. a minor change in fcl-core is ultimately a minor change in fcl-js)
We can consider pinning fcl-react-native as well (even though this library is currently unusable, so it's somewhat questionable whether this should be published at all).
Suggest A Solution
No response
What are you currently working on that this is blocking?
No response