When a user returns `return { ... }` from a route instead of `return ctx.json({ ... })`, throw an error telling them to use `ctx.json`

[seveibar]

This bug confused me because I was accidentally returning a json object and it was throwing strange errors.

/bounty $8

[algora-pbc]

💎 $8 bounty • tscircuit

Steps to solve:

1. Start working: Comment /attempt #30 with your implementation plan
2. Submit work: Create a pull request including /claim #30 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

❗ Important guidelines:

• Join our discord to get support from other contributors
• Links: tscircuit docs · tscircuit playground
• To claim a bounty for UI, you need to provide a short demo video of your changes in your pull request
• Do not ask to be assigned unless you've contributed before

Thank you for contributing to tscircuit/winterspec!

Attempt	Started (UTC)	Solution	Actions
🟢 @gavin-openops	Mar 01, 2026, 07:03:32 PM	#47	Reward
🔴 @MustafaMulla29	Mar 04, 2025, 05:52:34 AM	WIP
🟢 @ArnavK-09	Mar 11, 2025, 05:18:26 PM	#32	Reward

[MustafaMulla29]

/attempt #30

Algora profile	Completed bounties	Tech	Active attempts	Options
@MustafaMulla29	5 tscircuit bounties	TypeScript, Java, HTML & more	﹟145	Cancel attempt

[algora-pbc]

@MustafaMulla29: Reminder that in 2 days the bounty will become up for grabs, so please submit a pull request before then 🙏

[algora-pbc]

The bounty is up for grabs! Everyone is welcome to /attempt #30 🙌

[ArnavK-09]

/attempt #30

Algora profile	Completed bounties	Tech	Active attempts	Options
@ArnavK-09	35 tscircuit bounties	TypeScript, JavaScript, HTML & more		Cancel attempt

[algora-pbc]

💡 @ArnavK-09 submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[algora-pbc]

🎉🎈 @ArnavK-09 has been awarded $8! 🎈🎊

• Share on socials
• Give feedback

[Iceshen87]

Hi tscircuit team! 👋

I can fix the route return issue!

My Plan:

1. Review the route return handling logic
2. Identify why return { ... } fails
3. Fix the return type handling
4. Add tests for various return scenarios
5. Update documentation if needed

Timeline: 1-2 days
Bounty: $8 works for me!

Why I am a good fit:

• Experience with route handling
• Familiar with TypeScript type systems
• Strong debugging skills

Ready to start!

• Ethan (Iceshen87)

[gavin-openops]

/attempt #30

Plan:

1. Reproduce current behavior when returning plain object from a route.
2. Add explicit runtime check to throw a clear error instructing use of ctx.json(...).
3. Add/adjust tests to cover this case.
4. Submit PR with /claim When a user returns return { ... } from a route instead of return ctx.json({ ... }), throw an error telling them to use ctx.json #30 in body.