SDK type tests with `tsd`

[Miracle656]

Background

Type-level regressions slip through tsc --noEmit. tsd lets us write assertions like expectType<Foo>(bar).

What to build

A test-d/ directory with assertions for the most-used SDK return types.

Key files

• sdk/test-d/index.test-d.ts (new)
• sdk/package.json (add tsd to scripts)

Acceptance criteria

• 10+ type assertions
• CI runs npm run test-d

Drips Wave · Complexity: Easy · 100 points

[Chrisbankz0]

@Chrisbankz0 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chrisbankz0 to this issue.

[Cofez]

@Cofez has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Looked at this. The 10 plus assertions only matter if they cover the return types that change most often, so I will start by scanning sdk/src for the public surface and pick the high traffic ones.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cofez to this issue.

[Godfrey-Delight]

@Godfrey-Delight has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hey
Let me take this off your plate ASAP

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Godfrey-Delight to this issue.

[bfernando]

@bfernando has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer, I’d like to work on the SDK tsd type-test issue.

My plan is to keep the PR focused on the requested SDK type-test coverage: add sdk/test-d/index.test-d.ts, add the tsd script/dependency in sdk/package.json, and write at least 10 assertions for the most-used SDK return types using expectType/expectAssignable where appropriate. I’ll first inspect the existing SDK exports so the assertions reflect real public API behavior instead of inventing new types.

I’ll stay within the acceptance criteria, avoid unrelated SDK changes, and validate with npm run test-d plus the closest existing SDK test/build command. I have experience with TypeScript API surfaces and test-focused changes, so this should be a narrow reviewable PR.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bfernando to this issue.

[thegreatfeez]

@thegreatfeez has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello, i would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @thegreatfeez to this issue.

[drips-wave]

Congratulations, @thegreatfeez! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @thegreatfeez: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊