EVER SDK
Developer ToolsEver PlatformForum
  • Ever SDK
  • Quick start (JavaScript)
  • Add EVER to your backend
  • Reference
    • Types and Methods
      • Modules
      • Module abi
      • Module boc
      • Module client
      • Module crypto
      • Module debot
      • Module net
      • Module processing
      • Module proofs
      • Module tvm
      • Module utils
    • Error API
    • Error Codes
    • JavaScript Reference
    • Rust Reference
  • Samples
    • JavaScript Samples
  • guides
    • Installation
      • Add SDK to your App
    • Configuration
      • Endpoint Configuration
      • Message Expiration
      • Message Retry
      • Config Reference
    • Work with contracts
      • Add Contract to your App
      • Use your own Giver
      • Deploy
      • Run on-chain
      • Run ABI Get Method
      • Run Fift Get Method
      • Query/Subscribe for messages(events)
      • Decode Messages(Event)
      • External Signing
      • Emulate Transaction
      • Estimate Fees
      • Validate address, convert address
      • Monitor Messages
      • Trace message processing with REMP
    • Crypto
      • Mnemonics and Keys
    • Queries and subscriptions
      • Use-cases
      • How to work with net module
      • net.query syntax
      • Data pagination
      • Subscribe to Updates
      • Query Collection
      • Aggregate Collection
  • For Binding Developers
    • How to work with Application Objects in binding generators
    • JSON Interface to Ton Client
  • Links
    • Ever SDK repository
    • AppKit JS documentation
Powered by GitBook
On this page
  • Node.js
  • Web

Was this helpful?

  1. guides
  2. Installation

Add SDK to your App

PreviousInstallationNextConfiguration

Last updated 1 year ago

Was this helpful?

|

Node.js

Our library is fully-annotated with .d.ts files so we recommend to write your applications in Typescript.

Let's start with a clean npm project.

mkdir hello
cd hello
npm init -y

Now lets install core package and bridge package for Node.js

npm i --save @eversdk/core
npm i --save @eversdk/lib-node

If you want to use high-level package then install this package as well:

npm i --save @eversdk/appkit

You must initialize the library before the first use. The best place to do it is an initialization code of your application.

You need to attach the chosen binary module to the TonClient class. Create index.js file and add this code:

const {TonClient} = require("@eversdk/core");
const {libNode} = require("@eversdk/lib-node");

// Application initialization
TonClient.useBinaryLibrary(libNode)

Web

Our library is fully-annotated with .d.ts files so we recommend to write your applications in Typescript.

Let's start with a clean project.

mkdir hello
cd hello
npm init -y

Installation

Now lets install core package and bridge package for Web

npm i --save @eversdk/core
npm i --save @eversdk/lib-web

Important! Each time you run npm install the new version of the eversdk.wasm and index.js is downloaded. So you have to always update the eversdk.wasm inside your web package before publishing (starting local web server, creating web bundle etc.). If you use Webpack the best way is to use CopyPlugin.

npm i --save @eversdk/appkit

You must initialize the library before the first use. The best place to do it is in initialization code of your application.

You need to attach the chosen binary module to the TonClient class:

import { TonClient } from '@eversdk/core';
import { libWeb } from '@eversdk/lib-web';

TonClient.useBinaryLibrary(libWeb);

That's it! Now you are ready to create and

If you want to use high-level package then install this package as well:

configure TONClient object!
AppKit
AppKit
Node.js
Web