JavaScript SDKs and Support Tiers

The Errova JavaScript family is designed so most teams can use a framework-specific package instead of wiring the core SDK by hand. When a dedicated package exists, use it first (recommended) because it already understands the framework’s server/client boundaries, error wrappers, and lifecycle hooks.

Which Package Should You Install?

• Next.js: Next.js Setup using @errova/sdk-next
• Node.js or Express: Node.js and Express Setup using @errova/sdk
• Nuxt 3: Nuxt Setup using @errova/sdk-nuxt
• NestJS: NestJS Setup using @errova/sdk-nestjs
• Remix: Remix Setup using @errova/sdk-remix
• SvelteKit: SvelteKit Setup using @errova/sdk-sveltekit
• React, Vue, or Angular browser apps: React, Vue, and Angular Setup
• Other JS runtimes or custom SSR: use @errova/sdk directly.

Current Support Tiers

• Stable: @errova/sdk and @errova/sdk-next. Release expectations include conformance, smoke, unit tests, and release gates.
• Beta: @errova/sdk-remix, @errova/sdk-sveltekit, @errova/sdk-nuxt, and @errova/sdk-nestjs. Release expectations include conformance, unit tests, and release gates.
• Experimental: @errova/sdk-react, @errova/sdk-vue, and @errova/sdk-angular. Release expectations include unit tests and release gates.

Shared APIs Across the JavaScript Family

• Capture calls: captureException, captureMessage, and captureLog
• Context helpers: setUser, clearUser, withScope, and pushScope
• Lifecycle helpers: flush, close, and Client
• SDK-wide metadata: dsn, environment, release, and optional dsnSecret

Cross-Runtime Rules That Matter

• Keep ERROVA_DSN_SECRET server-only. Never expose it to browser bundles.
• Set environment and release on day one, not after rollout.
• Use short-lived job safeguards such as flush before process exit when appropriate.
• Review DSN Keys and Signed Ingest before you choose browser versus backend credentials.