You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tutorials still teach the deprecated stellar contract bindings typescript command #2968
What's wrong:
These pages tell readers to run stellar contract bindings typescript. The CLI marks that command deprecated and points to the JS SDK instead (stellar-cli reference on this site). It also still generates packages pinned to an older SDK major, not v17 (see the @stellar/stellar-sdk range in the CLI's TypeScript template), so apps that follow these pages get a second, older SDK copy next to v17.
Change needed:
Teach the SDK's own generator on each page, and say which SDK major the generated package uses.
Each tutorial's binding step runs with npx @stellar/stellar-sdk generate and the generated package installs @stellar/stellar-sdk 17.x.
npm ls @stellar/stellar-sdk in the tutorial project shows one copy.
No page outside docs/tools/cli/stellar-cli.mdx (generated from the CLI) tells readers to run the deprecated command.
pnpm validate passes.
Why it matters: At HackMeridian 2026, apps that generated bindings this way ended up with an older SDK copy next to v17; one team pinned its whole app to an older major because of it.
Related:#2561 (adds the generator to the client SDKs page), #2564 (cross-links; mentions the generator for fully-typed-contracts.mdx), #2960 (frontend guide).
PR #2985 fixes 5 of the 7 pages. Its checks pass. It says "Refs #2968", so this issue stays open.
The SDK generator is not a drop-in swap. Its output has no networks export, it ignores CLI aliases, and it turns _ into - in package names. The PR handles these on each page.
@kaankacar@ElliotFriend, one decision is needed: how should the 2 pages that depend on a companion repo change?
docs/build/apps/guestbook/bindings.mdx follows ElliotFriend/ye-olde-guestbook. With the SDK generator, the package becomes ye-olde-guestbook. It has no networks.testnet, and it does not re-export the SDK. Options:
A. Update the repo and the page together.
B. Keep the page as is and add a deprecation note.
docs/build/guides/dapps/soroban-contract-init-template.mdx:88 describes initialize.js in stellar/soroban-astro-template. That repo is archived and still runs the CLI command, so the line is accurate. Options:
A. Leave it.
B. Rewrite the page so it no longer depends on the archived template.
Activity
stellar-doxie commentedon Nov 1, 2026
🤖 Automated message from the Stellar Triage Bot.
I saw this issue. Nobody has called me in yet, so I will not work it now.
How to reach me:
/triage, add thebot:takelabel, or assign @kaankacar, @ElliotFriend or @wmendes./triage stop. People with write permission can also add thebot:hands-offlabel.oceans404 commentedon Nov 1, 2026
/triage
stellar-doxie commentedon Nov 1, 2026
🤖 Automated message from the Stellar Triage Bot.
Working this because @oceans404 added bot:take.
I am checking each listed page against the CLI and the JS SDK v17 generator now.
stellar-doxie commentedon Nov 1, 2026
🤖 Automated message from the Stellar Triage Bot.
Working this because @oceans404 added bot:take.
PR #2985 fixes 5 of the 7 pages. Its checks pass. It says "Refs #2968", so this issue stays open.
The SDK generator is not a drop-in swap. Its output has no
networksexport, it ignores CLI aliases, and it turns_into-in package names. The PR handles these on each page.@kaankacar @ElliotFriend, one decision is needed: how should the 2 pages that depend on a companion repo change?
docs/build/apps/guestbook/bindings.mdxfollowsElliotFriend/ye-olde-guestbook. With the SDK generator, the package becomesye-olde-guestbook. It has nonetworks.testnet, and it does not re-export the SDK. Options:docs/build/guides/dapps/soroban-contract-init-template.mdx:88describesinitialize.jsinstellar/soroban-astro-template. That repo is archived and still runs the CLI command, so the line is accurate. Options: