George
George
@mahnunchik give it a go in the [`upgrade-nacl`](https://github.com/stellar/js-stellar-base/tree/upgrade-nacl) feature branch (see ce3ff0b).
> Deployments fail due to this issue, stellar SDK becomes very painful to use. Is there a way we can fix this on the main package? The library is an...
Awesome, looks great to me! I updated the issue to have a checklist to track progress.
Thanks for bringing this thread out from the depths, guys, and documenting the solution @corymsmith :pray: I imagine this is because `sodium-native` fails to compile, which you can (probably) work...
Have you experimented with the [HTTP/2 adapter](https://github.com/uibakery/axios-http2-adapter#usage)? I haven't tried it yet myself, but it should be possible to override the default adapter like so: ```typescript import { Horizon }...
Eesh, this is bad. I will look your suggestions as well as packaging the SDK in multiple formats.
Hmm I'm surprised this even worked on Node honestly. It should be `import * as StellarSdk from ...` everywhere ever since the Webpack 5 refactor.
I'm going to close this issue as closed in v9.0.0-beta. Please reopen (or, better yet, comment on #584) if there is more you'd like to see.
@sreuland there's also stellar/soroban-cli#61 which is the Rust client side of things. I think JS is lower priority?
There is an additional schema change: the getLedgerEntries RPC response will use liveUntilLedgerSeq rather than expirationLedgerSeq in the final build (ref: stellar/soroban-tools#1029)