How mystenlabs/ts-sdks works
Main system domains and components
• Monorepo “Root”
– Package manager & workspace: pnpm, pnpm-workspace.yaml
– Monorepo runner: TurboRepo (turbo.json)
– Lint/build/test scripts (package.json at root)
– CI/CD orchestrator: GitHub Actions workflows under .github/workflows
• SDK Packages
By logical area:
1. Core client & transport
– packages/typescript/src/client
– packages/graphql-transport
– packages/utils
– packages/bcs
2. Cryptography & key management
– packages/typescript/src/cryptography
– packages/signers (aws, gcp, ledger, webcrypto)
– packages/seal (homomorphic, encryption)
– packages/move-bytecode-template (template engine)
3. Transaction building & codegen
– packages/codegen
– packages/kiosk
– packages/deepbook / deepbook-v3
– packages/zksend
4. Wallet & UI kits
– packages/dapp-kit
– packages/dapp-kit-next
– packages/create-dapp (CLI + templates)
– packages/enoki / enoki-connect / slush-wallet / window-wallet-core
– packages/wallet-standard
5. Data layers & misc tools
– packages/mvr-static (static builders)
– packages/utils
• Documentation site
– packages/docs (Next.js + MDX)
– Content pulls from packages’ typedoc.json and readmes
• Test infrastructure
– Unit tests: Vitest, Jest in each package
– E2E tests: testcontainers + Docker
• External services
– Docker daemon (for e2e testcontainers)
– GitHub (source host, Actions runner)
– npm registry (package publishing)
Inter-package relationships
– Core client (typescript) ← uses → BCS, cryptography, transport, utils
– codegen ← reads schemas → graphql-transport, Move modules in tests → generates TS code
– dapp-kit-next and dapp-kit ← both import → typescript client & wallet-standard
– create-dapp CLI ← scaffolds → template projects (that pull in dapp-kit or enoki)
– enoki-connect / window-wallet-core → provide wallet-channel abstraction consumed by UI kits
– kiosk ← uses → BCS + client transport to build kiosk transactions
• Test harness dependencies
– E2E tests ← orchestrated by → testcontainers (Docker)
– Unit tests ← run via → Vitest/Jest configured in each package
Architectural patterns & design principles
• Monorepo modularity: each package is a self-contained library with its own tsconfig, README, tests
• Shared infrastructure: build scripts (packages/build-scripts), shared ESLint and Prettier configs
• CI/CD pipelines: parallel & incremental builds via TurboRepo; custom workflows for publishing changesets
• Separation of concerns:
– Core blockchain client
– Cryptography & key handling
– Transaction builders and code generation
– Wallet connectivity & UI
– Documentation
Special notes for this monorepo
– Emphasize the workspace root orchestrator (pnpm + turbo) as the entry point for builds/tests
– Capture shared-config layers (.eslintrc.js, prettier.config.js, changesets at .changeset/)
– Show how create-dapp, enoki, and slush-wallet provide templates or demo dapps that depend on core SDKs
– Illustrate documentation site pulling in typedoc outputs from each package