Package Catalog¶

Flueco is published as focused packages. Choose the package by capability, then check its page for installation, provider prerequisites, and limitations. Installing a package alone does not register it in the application container.

Application and foundations¶

flueco: app-oriented bundle, kernel defaults, and UI services.
flueco_core: contracts and foundational services.
flueco_cli: command-line app scaffolding.

Use flueco for the integrated app surface; use flueco_core when you want to compose the foundation and integrations yourself. The CLI is a development tool, not an app runtime dependency.

Integrations¶

flueco_get_it: GetIt service container.
flueco_dio: Dio HTTP client.
flueco_auto_route: AutoRoute router adapter.
flueco_messaging: event-handling adapter.
flueco_hive: Hive-backed secure-storage contract implementation.
flueco_shared_preferences: shared_preferences local-storage adapter.
flueco_theming: theme and appearance services.

Adapters generally require both a provider and a prerequisite instance/configuration. For example, Dio needs DioBaseOptionsProvider; AutoRoute needs a RootStackRouter; shared preferences needs SharedPreferences; Hive needs HiveSecureStorageGetInstanceConfig; theming needs local storage and event handling.

Optional features¶

flueco_auth: authentication contracts and orchestration.
flueco_auth_basic: basic authentication strategy.
flueco_auth_token: token authentication strategy.
flueco_auth_dio_interceptor: authentication for Dio requests.
flueco_state_management: Provider-based view-model state APIs.

The flueco barrel re-exports core, selected adapters, and their upstream APIs. It does not re-export the auth packages, state-management package, or CLI. Verify your resolved package versions and transitive dependencies using Compatibility. Start with Manual installation, then follow the capability guide for the service you intend to use. For AI-assisted development workflows, see AI agent skills.