Practical overview
When it fits
Use it when developing a web, Node.js or React Native application that needs a JavaScript client for Everscale, Venom, TON or Gosh.
Who it is for
- Web developers building applications for the listed TVM-compatible networks.
- Node.js developers integrating a blockchain client into services.
- React Native developers building mobile applications that connect to those networks.
Documented uses
- Add a shared blockchain client library and a runtime-specific bridge to a JavaScript application.
- Initialize TonClient with the bridge for the target platform.
- Use client modules, including the documented crypto example for generating random signing keys.
Requirements & limits
The repository is public and identifies the project as licensed under Apache-2.0. Its installation instructions use npm packages.
- Choose the bridge that matches the target runtime: Node.js, browser or React Native.
- The README identifies Node.js 14 LTS as the version used in testing pipelines and the version for which stable operation is stated.
- Browser setup uses WASM and, by default, a separate worker; the documented configuration can change the WASM URL or disable the worker.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and initialize the browser client
Add the shared SDK and web bridge to a browser application and attach the bridge to TonClient.
Before you start
- Node.js 14 LTS is the version the repository identifies for stable operation.
- npm and a web application project.
Steps
Install @eversdk/core and @eversdk/lib-web with npm.
Import TonClient from @eversdk/core and libWeb from @eversdk/lib-web.
In application initialization code, call TonClient.useBinaryLibrary(libWeb).
Expected outcome
The web bridge is attached to TonClient for use by the application.
Guide limitations
- The web bridge downloads eversdk.wasm and index.js during npm installation; update eversdk.wasm in the web package before publishing.
- The bridge loads the WASM module from /eversdk.wasm by default; the README documents configuring another URL.
- The documented setup step does not cover connecting to a specific network or implementing an application flow.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- everx-labs/ever-sdk-js · Official homepage title · retained in its source language

