-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDK Modernization #69
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huzzah!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work, a veritable clinic, my approval is lightweight, look forward to porting this to soroban
branch, you mentioned it resolves the webpack issue on js-xdr dependency from stellar-base:9.0.0-soroban.1
, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! 🎉
Seems like soroban-client no longer ships with TypeScript types. Is this change the cause? |
Why use babel at all? Why not just build with TypeScript? |
that was a bug; #86 should have fixed it (part of v0.7.0) as for Babel, I think we still need it to be able to control the output targets? |
You mean this? https://www.typescriptlang.org/tsconfig#target I'll try 0.7.0, especially now that futurenet has been updated! Thanks. |
Yeah so that one is nice but it's not granular enough, I think. Babel lets you target specific browser versions, market share, etc. Actually, thinking about it more, we could probably get away with just using |
In line with stellar/js-stellar-sdk#814, this refreshes the build system to use the latest&greatest in JS build pipelines.
It also bumps the minor version to
v0.6.0
.