Runtime setup
Each guide starts from an empty directory and includes installation commands, configuration and public price examples.
Server-side JavaScript and TypeScript
- Node.js / JavaScript: ES modules and CommonJS.
- Node.js / TypeScript: strict type checking and build/run commands.
- Next.js: a server-side price route.
- Bun and Deno: npm dependencies and runtime commands.
- Cloudflare Workers: public REST reads and an optional authenticated order route.
Keep private operations on your server. Compressed WebSocket messages require DecompressionStream; check support in the runtime you deploy.
Browser applications
The React and Vite recipes use the SDK's browser mappings and include EventEmitter resolution. Keep the supplied files together and omit Node-only agents. These examples contain no credentials.
Browser REST access depends on HTX CORS policy, network and regional availability. Use a protected server route when direct requests are unavailable. A development proxy is not a production backend.
React Native and Expo
The Expo recipe includes Metro configuration and import polyfills. It does not polyfill DecompressionStream, which the HTX stream requires. Confirm that API exists on your device runtime before using the stream, or relay prices through your backend.
Streaming lifecycle
The Node.js starter closes after the first valid price or a failure. Browser and mobile views close connections on unmount or Stop. The standalone guide stream runs until Ctrl+C. Automatic resubscription does not guarantee that missed state is replayed.