Choosing the Right SDK for Your Platform
Compare SDKs and pick the right one for your tech stack.
Available SDKs
| Platform | Package | Best For |
|---|---|---|
| Node.js | @lognitor/node | Server-side JS/TS — Express, Fastify, Hono, Next.js API routes, NestJS |
| Browser | @lognitor/browser | Client-side JavaScript — any web app, SPAs, vanilla JS |
| React | @lognitor/react | React apps — adds provider, error boundary, hooks on top of Browser SDK |
| Python | lognitor | Python apps — Django, Flask, FastAPI |
| PHP | lognitor/lognitor | PHP apps — Laravel, Symfony, WordPress |
| REST API | cURL / HTTP | Any language without an SDK, CI/CD scripts, testing |
Decision Guide
Building a Node.js backend? Use @lognitor/node. It includes middleware for Express, Fastify, Hono, Next.js, and NestJS.
Building a React frontend? Use @lognitor/react. It wraps the Browser SDK with LognitorProvider, LognitorErrorBoundary, and the useLognitor() hook.
Building a non-React frontend? Use @lognitor/browser directly. Works with Vue, Angular, Svelte, or vanilla JavaScript.
Full-stack Next.js? Use both — @lognitor/react for client components and @lognitor/node with createNextjsWrapper for API routes.
Language not listed? Use the REST API directly. Any language that can make HTTP POST requests works.
Batching, retries, PII redaction, breadcrumbs, user context, timers, heartbeats, and release tracking work the same across every SDK.