stacked_shared
1.4.2, released 2 years ago by filledstacks.com
Shared code between the stacked packages.
WASM-readyQuiet but busy
What it does
Contains all the code shared between the flutter and pure dart packages to avoid including flutter where it's not required. It integrates with get_it for dependency management.
AI-written summary of version 1.4.2, based on the package's README and metadata. Report an inaccuracy
Use it when
- You are using packages from the Stacked architecture ecosystem that rely on shared core code.
- You need the shared foundational classes used across stacked packages.
Skip it when
- You are not using the Stacked architecture ecosystem.
- You need a standalone dependency injection library without stacked dependencies.
Strengths
- Avoids including Flutter dependencies where pure Dart is sufficient.
- Centralizes shared utilities for the Stacked architecture.
Weaknesses
- Not intended for direct standalone use outside of the Stacked architecture ecosystem.
- Limited documentation for standalone usage.
Setup
- Kind
- Pure Dart
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 1
Not documented
Works with
Packages commonly used together with stacked_shared: ones it builds on, ones built on it, and its own family.
- get_itstacked_shared depends on itA fast, type-safe service locator for Dart and Flutter without BuildContext or code generation.
- stacked_hooksSame familyClasses that help use Flutter Hooks with the stacked package architecture.
- stackedBuilt on stacked_sharedA complete frontend architecture framework for building Flutter applications.
- stacked_generatorBuilt on stacked_sharedGenerates routing and dependency‑injection boilerplate for Stacked apps.
- stacked_servicesBuilt on stacked_sharedProvides default implementations of services for the Stacked architecture.
- stacked_themesBuilt on stacked_sharedManage multiple themes, dark mode, and theme persistence in Flutter applications.