routerino
0.8.1, released 10 months ago by tienisto.com
Imperative navigation extension for BuildContext without declarative patterns or build_runner.
What it does
Provides BuildContext extension methods to push, pop, and manage routes imperatively while automatically handling route names for Sentry integration. It avoids verbose declarative routing patterns and does not require code generation.
AI-written summary of version 0.8.1, based on the package's README and metadata. Report an inaccuracy
Use it when
- You prefer an imperative routing approach over a declarative setup like go_router
- You want type-safe navigation and results without using build_runner
- You need automatic route naming for error tracking services like Sentry
Skip it when
- You need advanced declarative deep linking and URL path synchronisation out of the box
- Your application relies heavily on obfuscation for production builds
Strengths
- Extremely low boilerplate for pushing and popping widgets
- No code generation step required
- Built-in type-safe results and Sentry integration support
Weaknesses
- Breaks if Flutter obfuscation is enabled because class names are used for route names
- Opinionated approach that replaces standard Navigator calls heavily
Setup
- Kind
- Flutter widgets
- Effort
- Low
- Code generation
- Yes (build_runner)
- Direct dependencies
- 0
Optionally wrap your app with RouterinoHome and set Routerino.navigatorKey for global context usage.
context.push(() => MyPage());Alternatives
Packages that do the same job and could replace routerino.
- go_router
Declarative routing package for Flutter based on Navigation 2 supporting deep links and URL-based navigation.
98Compare - auto_route
A Flutter package for declarative, strongly‑typed navigation with code‑gen support.
87Compare - qlevar_router
Router for Flutter with nested routes and navigation without context
80Compare - kaisel
A Dart 3-native Flutter router using sealed routes and pattern matching.
76Compare