app_runner
2.2.2, released 3 years ago by madbrains.ru
Configurator for controlled Flutter app initialization, error handling, and splash screen management.
WASM-ready
What it does
Provides a robust entry point structure to initialize asynchronous services before app startup, handle Dart and Flutter errors safely, and display custom splash screens without blocking.
AI-written summary of version 2.2.2, based on the package's README and metadata. Report an inaccuracy
Use it when
- You need to initialize asynchronous services like Firebase before running the app widget tree.
- You want centralized error handling for uncaught exceptions and Flutter errors.
- You want to show a custom splash screen during asynchronous pre-initialization.
Skip it when
- Your application relies on standard minimal runApp setups without complex pre-initialization.
- You are using a lower Flutter version than 3.10.0 (unless using package version 2.1.2 and below).
Strengths
- Simplifies safe zone configuration and error management.
- Allows pre-initialization of data before building the main app widget.
- Provides independent debug and release error screens.
Weaknesses
- Introduces custom abstractions over standard Flutter entry point logic.
- Requires updating configuration patterns when upgrading major package versions.
Setup
- Kind
- Flutter widgets
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 0
Replace standard main() implementation with appRunner configuration.
import 'package:app_runner/app_runner.dart';
import 'package:flutter/material.dart';
void main() {
appRunner(
RunnerConfiguration.guarded(
widgetConfig: WidgetConfiguration(
child: const MyApp(),
),
zoneConfig: ZoneConfiguration(
onZoneError: (Object error, StackTrace stackTrace) {},
),
),
);
}