TBDex WASM Release Documentation And Checklist

[nitro-neal]

TBDex WASM Release Documentation And Checklist

Repository Components

Core Components

• WASM-bound TypeScript TBDex Code
  • Location: tbdex-rs/bound/typescript

Example Implementations

1. Local Exemplars

   • PFI and Wallet implementations
   • Location: tbdex-rs/examples/hosted-wallet-ts

2. Front-end React Exemplar

   • Location: wasm-exemplar

NPM Packages

• Official Package (Pending)

  • Location: @tbdex/sdk
  • Status: Awaiting NPM_TOKEN secret configuration
  • Release Action: release-typescript.yml

• Test Package

  • Location: tbdex-wasm-test
  • Purpose: Rapid testing environment while awaiting official release

Priority Tasks

High Priority

• DID Web Implementation
  • Update Web5 Cli to be able to generate did web with configurable service endpoints
  • Create testing DID web with service endpoints to http://localhost:8082
  • Host on designated domain
  • Update exemplars to use DID Web
• Flow Implementations
  • Add Happy Path Flow to exemplar
  • Add Webhook Flow to exemplar
  • Add Cancel Flow to exemplar
• Bug Fixes
  • Resolve Get Exchange WASM Black hole error
  • Fix submitOrder and createExchange WASM black hole error
• NPM Publishing
  • Configure Github Action workflow
  • Created test npm package to unblock and test react excemplar
  • Add NPM_TOKEN secret to tbdex-rs repo
  • Execute release action
  • Add NPM Readme

Lower Priority

• Documentation Updates
  • Create README for Local Exemplar
  • Update WASM SDK README (can match Kotlin format)
  • Develop comprehensive NPM documentation
• Testing Improvements
  • Expand HTTP client unit tests
  • Add missing test vectors
• Package Refinements
  • Ensure proper type publishing for typescript
  • Verify complete package contents beyond minified JS
• Bugs
  • Fix transient failing errors because of did dht time out (switch to did web or mock)
  • Change wasm bundle script to work on ubuntu and macos (currently only works on mac)

Next Steps

1. Focus on completing high-priority items, particularly DID Web implementation
2. Address critical WASM black hole errors
3. Complete NPM publishing setup
4. Progress through documentation and testing improvements