Describe the bug
When attempting to create a package that manages building the complicated XDR objects required for Soroban, I am unable to use separate but identical versions of stellar-base to handle these XDR objects. The use case is the consumer (a dApp or node script, for example) likely already relies on soroban-client and/or stellar-sdk.
Expected behavior
The XDR object created by the dependency is valid
Additional context
The current workarounds are to re-export xdr that the dependency uses, or to have the package return the xdr objects as strings and expect the consumer to build them from the string.
Describe the bug When attempting to create a package that manages building the complicated XDR objects required for Soroban, I am unable to use separate but identical versions of
stellar-base
to handle these XDR objects. The use case is the consumer (a dApp or node script, for example) likely already relies onsoroban-client
and/orstellar-sdk
.For more context see the discussion in discord here: https://discord.com/channels/897514728459468821/1113560546705428600
What version are you on?
To Reproduce Steps to reproduce the behavior:
Expected behavior The XDR object created by the dependency is valid
Additional context The current workarounds are to re-export
xdr
that the dependency uses, or to have the package return the xdr objects as strings and expect the consumer to build them from the string.