
Sentry SDK for Dart & Flutter
https://github.com/getsentry/sentry-dart- Category
- Developer Tools
- Rank
- No. 363Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- getsentry
- GitHub
- 872 stars
- Latest release
- 10.0.0-alpha.5
- Date
About
Official Sentry SDK for Dart and Flutter. Capture crashes, performance traces, and screenshots from mobile and web Flutter apps.
What it does
This is a modular client library family for sending application telemetry to Sentry. Teams choose a core Dart or Flutter package, then add focused adapters for logging, networking, file access, databases, GraphQL, Supabase, Firebase Remote Config, or gRPC.
Why it's ranked here
The strongest argument is coverage without forcing every integration into one package. The repository pairs a core SDK with narrowly scoped adapters, native Flutter integrations, examples, microbenchmarks, package-specific CI, and a release process that distinguishes prerelease, latest, and field-tested stable builds.
What's good
The package boundaries match real application dependencies, including Dio, Drift, Hive, Isar, SQLite, logging, files, GraphQL, Supabase, Firebase Remote Config, and gRPC. Dart-only and Flutter packages have separate analysis and test workflows. Native SDK versions are explicitly tracked across Android, Apple, JavaScript, and native targets.
Tradeoffs
The broad monorepo creates coordination cost across many separately published packages and native dependencies. Dart-only and Flutter packages require different analysis and test commands. Formatter output can differ between local Dart and Flutter-bundled Dart versions. Package publishing also temporarily skips validation because of an implicit web dependency.
How to use it well
Choose it when a Dart or Flutter application already uses Sentry and needs telemetry connected to its actual framework and data stack. Start with the core package for your runtime, then add only relevant adapters. Treat the examples, package documentation, and stable release channel as operational guides. It does not supply the underlying HTTP, database, logging, or storage libraries.
Technical notes+
The root pubspec.yaml defines a non-published Melos workspace requiring Dart >=3.5.0 <4.0.0. melos.yaml discovers nested packages, separates Dart and Flutter analysis and tests, and points at .fvm/flutter_sdk. .craft.yml publishes thirteen packages to pub.dev and registers their SDK names, while temporarily setting skipValidation: true for the pub-dev target. docs/sdk-versions.md maps each Flutter SDK line to Android, Cocoa, JavaScript, and Native SDK versions. packages/flutter/microbenchmarks/linux/runner/main.cc and packages/flutter/microbenchmarks/windows/runner/main.cpp show native desktop benchmark runners. docs/new-package-release-checklist.md requires examples, public API exports, documentation, changelogs, licensing, package metadata, analysis configuration, and dedicated CI for new packages.
Observed
- License
- MIT License
- Primary language
- Dart, with native C++ runner code for Flutter desktop targets
- Packaging
- Melos monorepo with separately published pub.dev packages
- Interface
- Client libraries and integration packages for Dart and Flutter applications
- Platform support
- Dart and Flutter, including web, Android, Apple platforms, Linux, and Windows surfaces
- Package structure
- Core Dart and Flutter SDKs plus adapters for logging, HTTP, files, databases, GraphQL, Supabase, Firebase Remote Config, and gRPC
- Toolchain requirement
- Workspace requires Dart 3.5 or newer and earlier than Dart 4
Read from README.md, pubspec.yaml, packages/flutter/microbenchmarks/linux/runner/main.cc, packages/flutter/microbenchmarks/windows/runner/main.cpp, docs/sdk-versions.md, docs/new-package-release-checklist.md, packages/flutter/example/linux/main.cc, packages/flutter/example/windows/runner/main.cpp, LICENSE, AGENTS.md, CLAUDE.md, .craft.yml, .pubignore, melos.yaml, agents.toml.
What it can do
Capture application crashes
Runtime errors and exceptions in Dart/Flutter apps → Crash reports with stack traces and error details
Monitor application performance
Performance data from Flutter app execution → Performance traces and metrics
Capture screenshots on errors
Error events in mobile and web Flutter apps → Screenshots of app state when errors occur
Track user sessions
User interaction data from Flutter apps → Session analytics and user journey data
Send error reports to Sentry platform
Collected crash and error data → Centralized error reports in Sentry dashboard
Monitor real-time application health
Live application metrics and error rates → Application health status and alerts
Tags
Tech Stack
Media

Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.