Skip to content

Publish tunnels-sdk WASM as downloadable artifact and/or npm package #7

@aaronparsons-dev

Description

@aaronparsons-dev

Problem

The Tunnels SDK (tunnels-sdk) compiles to WASM for browser-based key management and transaction signing. However, there is no pre-built artifact available. A third-party developer building an application on the protocol cannot compile the SDK without the full Rust toolchain and the protocol source tree.

Expected

A developer building on Tunnels should be able to:

  1. Download a pre-built .wasm binary from the GitHub release assets, or
  2. Install an npm package (e.g., @tunnelsprotocol/sdk) that includes the WASM binary and TypeScript bindings

Suggested approach

Short term: Attach tunnels_sdk_bg.wasm and the generated JS glue code to the v0.1.0 release assets.

Longer term: Publish an npm package with the WASM binary, TypeScript type definitions, and a minimal wrapper for loading/initializing the module in browser environments.

Context

This gap was identified while preparing to build The Garage (the first application on the protocol) from the perspective of a third-party developer who has access only to the published documentation and JSON-RPC API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions