// the find
getsentry/sentry-javascript
Official Sentry SDKs for JavaScript
The official Sentry SDK monorepo for JavaScript. It publishes `@sentry/core` plus around two dozen platform packages (browser, node, React, Vue, Next.js, Cloudflare, and others) that report errors and traces to Sentry. It is aimed at anyone who wants production error monitoring in a JavaScript or TypeScript app and would rather use the maintained client than write their own.
- `@sentry/core` holds the shared interfaces, scope handling, and transport logic, and the platform packages are thin layers over it. A fix in core reaches every platform in one change, which is what keeps a repo this wide workable.
- Bundle size is treated as a build-time constraint. The root `.size-limit.js` and a dedicated workflow for bumping limits mean a change that grows the browser payload has to be justified rather than slipping in unnoticed.
- Browser behavior is exercised in real browsers. `dev-packages/browser-integration-tests` runs Playwright suites for loader-script setups, fetch error handling, and feedback flows, which catches integration breakage that unit tests miss.
- The README is mostly a link index. The only setup example is a generic `Sentry.init` snippet, and real configuration lives in each platform package's own docs, so a newcomer has to identify the right one of two dozen packages before they can start.
- Maturity is uneven, and the README says so in places. `@sentry/effect` is labeled Alpha, and Electron, React Native, and Capacitor are maintained in separate repositories, so this repo does not show the whole picture for every platform.
- Upgrades cost attention. The version support policy promises fixes for older versions 'based on community demand and usage', which is not a schedule. If you pin an old major, plan to read MIGRATION.md before you move.