Releases: meshline-network/sdk
Release list
Meshline.Sdk 1.1.0
Full Changelog: v1.0.0...v1.1.0
TypeScript SDK 0.1.0-alpha.2
Full Changelog: v1.1.0...typescript-v0.1.0-alpha.2
Meshline TypeScript SDK 0.1.0-alpha.1
Initial alpha release of the Meshline TypeScript SDK, published on npm as 0.1.0-alpha.1.
The SDK provides account and device management, profiles and contacts, encrypted direct messages, conversations, channels, and groups. Applications select storage and transport adapters for their runtime.
Packages
| Package | Purpose |
|---|---|
| @meshline/sdk | Runtime-independent ESM core and TypeScript declarations |
| @meshline/storage-node | Node.js SQLite storage |
| @meshline/transport-node | Node.js HTTP and WebSocket adapters |
| @meshline/storage-browser | Browser IndexedDB storage |
| @meshline/expo | Expo SQLite, cryptographic randomness, HTTP, and native WebSocket adapters |
For a Node.js application:
npm install @meshline/sdk@0.1.0-alpha.1 @meshline/storage-node@0.1.0-alpha.1 @meshline/transport-node@0.1.0-alpha.1Start with the quick start, then follow the application guides and examples.
Requirements and alpha limitations
- Node.js adapters require Node.js 24 or later. Browser storage requires a secure origin, IndexedDB, and Web Locks.
- Windows Node.js and Android 11/API 30 with Hermes have been exercised. Linux runtime and iOS native build/runtime validation remain pending; this is not a claim of support for every device or OS version.
- Expo requires a native development or production build; Expo Go is not supported. Follow the pinned dependency requirements, Android compatibility command, and native rebuild instructions in the platform guide.
- Windows Playwright WebKit has a known HTTP cookie-omission failure. Browser WebSocket cookie behavior is controlled by the browser; use a relay origin without cookies. See the platform guide before deploying browser transport.
- This is an alpha release. Pin the package version when evaluating it. The npm
alphatag points to this version; npm also assignedlateston the first publication.
The five attached npm archives are the exact files published to npm. SHA256SUMS contains their checksums. Source files and a forced TypeScript rebuild were compared with the published archives; an independent npm installation passed declaration checks and the Node.js persistence/restart smoke test. This release does not add new native-device validation.
Meshline.Sdk 1.0.0
Meshline.Sdk 1.0.0 is the first .NET SDK release for applications using the Meshline protocol.
Install
Target .NET 10 and install the NuGet package:
dotnet add package Meshline.Sdk --version 1.0.0Included capabilities
- Account setup and recovery, device authorization, profiles, contacts, and home-relay migration.
- End-to-end encrypted direct and group messaging, and public channels.
- HTTP and WebSocket relay connectivity with background synchronization and reconnection.
- SQLite persistence, local conversations, and pending-operation recovery.
- Protocol models, Canonical JSON, signatures, encryption, message bodies, and attachment references.
Integrate with your application
The application supplies account signing (IAccountSigner), relay registry access (IRelayRegistry), and local secret protection (ISecretProtector). Use MeshlineClient to coordinate the components, or compose them independently.
Start with the integration guide and examples. Use the network reference and Registry contract hash for the Meshline network you intend to join.
Validation and limitations
All 542 offline tests passed, covering protocol and cryptographic vectors, transport, SQLite persistence, client workflows, and lifecycle behavior. Live-relay interoperability and mobile, browser, and NativeAOT environments remain unvalidated. Applications handle content retrieval and rendering.
This SDK release does not change the Protocol 1.0 specification draft status. The TypeScript SDK is planned; the Relay and WPF reference client are not yet public.