# Coverage and compatibility

Choose the actual runtime entry and understand the boundaries of automatic detection.


JavaScript frameworks and runtimes: Next.js, React, Vue, Svelte, Node.js, NestJS, Cloudflare; repository integration through GitHub.

## Runtime matrix

| Application | Entry / integration | Important boundary |
| --- | --- | --- |
| Browser JavaScript | `@everock/sdk` | Browser errors, supported HTTP capture, vitals, optional replay/plugins |
| Next.js | `@everock/next` | Browser provider plus separate server instrumentation and ingest route |
| Vite React/Vue/Svelte/Solid | `@everock/vite` | Build plugin plus client initialization |
| Node Express/Fastify/Koa | `@everock/sdk/node` | Node process and supported HTTP/database integrations |
| NestJS | `@everock/nest` | Node SDK plus Nest interceptor |
| Cloudflare Workers | `@everock/sdk/edge` | Fetch wrapper and invocation-lifetime delivery |
| OpenTelemetry JavaScript | `@everock/sdk/opentelemetry` | Compatible span exporter, not a generic OTLP HTTP endpoint |
| Native Swift / Kotlin | No dedicated package in this repository | Do not describe browser replay or JS instrumentation as native mobile coverage |

Astro, SvelteKit, Nuxt, and other hybrid frameworks can have both browser and server runtimes. Instrument the browser entry and the appropriate Node/edge runtime separately. A framework name by itself does not prove all adapters have been tested.

## What automatic means

Instrumentation observes execution inside the configured runtime. It does not read provider management accounts, inspect every remote database/server, run paid third-party APIs, or backfill events from before installation.

## Package availability

Package names and entry points here match this source repository. CLI and MCP are currently private workspace packages. Publishing and testing registry distribution is a separate release step; a package version in a manifest is not proof that it is available on npm.

## Validate your stack

Verify a handled error, an incoming and outgoing request where applicable, environment/release labels, privacy filters, and shutdown delivery. Test an actual deployed worker and real browsers before claiming support for those environments.