JavaScript
JavaScript SDKs
Everything you need to integrate the embedded wallet into a web application, from a low-level TypeScript SDK to a drop-in React UI kit.
Pick the layer that matches your stack — each layer builds on the one below it:
| Layer | Package(s) | Use when |
|---|---|---|
| JS-Core | @nexus-cross/crossx-sdk-core | Vanilla JS / TS, any framework, Node.js. Full control over auth, wallet, signing, and RPC. |
| JS-React | @nexus-cross/crossx-sdk-react | React apps that do not use wagmi. Provider + hooks (useAuth, useWallet) over the Core SDK. |
| JS-Wagmi | @nexus-cross/crossx-sdk-wagmi | Apps built on wagmi / viem. Exposes the embedded wallet as a standard wagmi connector. |
| App Launcher (Connect Kit) | @nexus-cross/connect-kit-react · @nexus-cross/connect-kit-wagmi · @nexus-cross/connect-kit-core · @nexus-cross/dapp-ui | You want a complete, production-ready wallet UI — connect modal, wallet info panel, portfolio, buy/send/bridge — with a few lines of setup. |
Which one should I use?
- Building a DApp and want wallet UI out of the box? Start with the App Launcher (Connect Kit). It wraps the SDKs below and ships the full CROSS ecosystem UI: connect button + modal, wallet info, portfolio, on-ramp, bridge, and more.
- Already on wagmi and want to keep your own UI? Use JS-Wagmi to add the embedded wallet as one more connector.
- React without wagmi? Use JS-React.
- No React at all, or server-side / game-engine WebView integration? Use JS-Core directly.
All layers share the same project ID, OAuth-based login (Google / Apple / JWT), PIN-protected embedded wallet, and chain registry.
Updated 2 days ago