Submodules (TS)

[bradleyshep]

Description of Changes

Adds reusable TypeScript submodules for SpacetimeDB, including:

• Agents
• API keys
• Authentication
• Cron
• Crypto
• Files
• Grid
• Lobby
• PostHog
• Presence
• Rate limiting
• Resend
• Retry
• Stripe

Each submodule includes package metadata, documentation, tests, and an example where applicable. The change also adds shared example UI code and connects the packages to the existing pnpm workspace, lint configuration, and CI workflow.

Example screenshots

Agents

API Keys

Auth

Cron

Files

Grid

Lobby

PostHog

Presence

Rate Limit

Resend

Stripe

API and ABI breaking changes

No existing API or ABI is changed. This PR adds new TypeScript package APIs.

Expected complexity level and risk

3/5

The change is large, but most code is isolated in new top-level submodule folders. The main risk is in scheduled work, native HTTP routes, and external provider integrations such as Stripe, Resend, and PostHog.

Testing

• Build all submodule packages and examples
• Run submodule unit and integration tests
• Generate and verify TypeScript client bindings
• Run lint and formatting checks
• Test applicable examples against a local SpacetimeDB instance
• Review the public package APIs and documentation
• Run credentialed provider smoke tests in the reviewer environment

Rollback safety impact

n/a

[cloutiertyler]

I think we need to break this into multiple PRs:

1. A PR with just the high priority submodules that do not depend on fetch/async procs, and whose API we've carefully designed (e.g. cron, resend, agents ?)
2. High priority ones that depend on fetch/async procs
3. Low priority/nice to have ones ones (e.g. grid, lobby, api-keys)

Ale and I would like to make sure the APIs for all of these submodules are carefully designed because we're going to have to maintain them indefinitely. And with 1035 files in this PR it's a little too overwhelming to review.

[aasoni]

We also want to make sure we use the correct conventions for typescript variable naming. I saw at least in one README an example code that used snake case for variable names. We should make sure both the code and the README examples have variable names consistent with the typescript conventions. Usually:

Style	Category
UpperCamelCase	class / interface / type / enum / decorator / type parameters / component functions in TSX / JSXElement type parameter
lowerCamelCase	variable / parameter / function / method / property / module alias

[bradleyshep]

Split this into six smaller PRs, grouped by dependencies and review scope:

• Add core TypeScript submodules: cron, retry, rate-limit, and crypto #5903 — Core: cron, retry, rate-limit, crypto, and shared example support.
• Add Resend transactional email submodule #5904 — Email: Resend.
• Add agents, authentication, and file submodules #5905 — Agents, auth, and files.
• Add Stripe payments submodule #5906 — Payments: Stripe.
• Add PostHog analytics submodule #5907 — Analytics: PostHog.
• Add grid, lobby, presence, and API key submodules #5908 — Grid, lobby, presence, and API keys.

The integration PRs build on #5903. The final group builds on #5905 because its examples use auth and files. Each PR includes its documentation, tests, and examples.

Closing this PR in favor of those focused reviews. The original branch remains available as a reference.