Port Binding Generation

[Ryang-21]

• Implements contract binding generation functionality that previously existed in the stellar-cli
• Adds a CLI to facilitate the binding generation
• Addresses Move typescript binding generation from the stellar-cli to the js-stellar-sdk #1154

CLI Usage Examples

From a local WASM file

npx @stellar/stellar-sdk generate \
  --wasm ./path/to/wasm_file/my_contract.wasm \
  --output-dir ./my-contract-client \
  --contract-name my-contract

From a WASM hash on the network

npx @stellar/stellar-sdk generate \
  --wasm-hash <hex-encoded-hash> \
  --rpc-url https://soroban-testnet.stellar.org \
  --network testnet \
  --output-dir ./my-contract-client \
  --contract-name my-contract

From a deployed contract ID

npx @stellar/stellar-sdk generate \
  --contract-id CABC...XYZ \
  --rpc-url https://soroban-testnet.stellar.org \
  --network testnet \
  --output-dir ./my-contract-client

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	commander@​14.0.2

View full report

[Shaptic]

Looks awesome so far! Mostly minor comments below, gonna try it out right now too.

[Shaptic]

Should we just fetch and write the official one, instead?

[Shaptic]

Couple more thoughts after running it on a side-project of mine

[github-actions]

Size Change: +2.24 MB (+5.26%) 🔍

Total Size: 44.8 MB

Filename	Size	Change
dist/stellar-sdk-minimal.js	5.93 MB	+360 kB (+6.46%)	🔍
dist/stellar-sdk-minimal.min.js	5.05 MB	+200 kB (+4.13%)
dist/stellar-sdk-no-axios.js	5.93 MB	+360 kB (+6.46%)	🔍
dist/stellar-sdk-no-axios.min.js	5.05 MB	+200 kB (+4.13%)
dist/stellar-sdk-no-eventsource.js	6.18 MB	+360 kB (+6.18%)	🔍
dist/stellar-sdk-no-eventsource.min.js	5.26 MB	+200 kB (+3.96%)
dist/stellar-sdk.js	6.18 MB	+360 kB (+6.18%)	🔍
dist/stellar-sdk.min.js	5.26 MB	+200 kB (+3.96%)

_{compressed-size-action}

[Ryang-21]

Feedback should be addressed. The sdk now generates the same bindings as the cli besides one difference in how ScOptions are handled. The cli typed it as T | undefined but that is incorrect as the Spec decodes it as null this is problematic if users are strict equality checking the result against undefined. cc. @mootz12 @leighmcculloch

[Copilot]

Pull request overview

This PR implements contract binding generation functionality, porting it from stellar-cli to the JavaScript SDK. It adds a CLI tool and programmatic API to generate fully-typed TypeScript client code from Stellar smart contract specifications.

Changes:

• Adds BindingGenerator class for generating TypeScript bindings from contract specs
• Implements CLI with generate command supporting local WASM, network hash, and contract ID sources
• Includes comprehensive unit, integration, and e2e tests with snapshot testing

Reviewed changes

Copilot reviewed 24 out of 27 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/bindings/generator.ts	Core binding generator with factory methods for creating from WASM/network sources
src/bindings/client.ts	Generates typed Client class with contract methods
src/bindings/types.ts	Generates TypeScript interfaces for contract structs, enums, and unions
src/bindings/utils.ts	Utility functions for type mapping, identifier sanitization, and import generation
src/bindings/wasm_fetcher.ts	Fetches contract WASM from network via RPC
src/cli/index.ts	CLI implementation with network configuration and option parsing
src/cli/util.ts	CLI utility functions for file I/O and contract name derivation
test/integration/bindings.test.ts	Unit tests for binding generation
test/e2e/src/bindings.test.ts	E2e tests for generated bindings compilation and runtime
test/e2e/src/cli.test.ts	E2e tests for CLI functionality

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Shaptic]

Should this be a specific commit SHA?

[janewang]

Herculean effort 💪

Thank you @Ryang-21 👏👏👏