orbital 0.1.1
orbital: ^0.1.1 copied to clipboard
Full Orbital package that reexports core, injector and router.
orbital #
Convenience bundle that reexports the full Orbital runtime from a single import.
When to use this package #
Use orbital when you want:
- one import for core contracts, injector and router
- the default scope runtime available immediately
- the convenience
enableOrbitalDevtools(...)wrapper in the same package
import 'package:orbital/orbital.dart';
Choose the individual packages when you want tighter dependency boundaries:
orbital_corefor contracts, logging and debug primitivesorbital_injectorfor scope trees without Flutter routingorbital_routerfor Flutter navigation on top of Orbital scopesorbital_devtoolsfor the Flutter DevTools extension UI
Quick start #
final logger = OrbitalLogger();
enableOrbitalDevtools(logger: logger, appId: 'my-app');
MaterialApp.router(
routerConfig: OrbitalApp.router(
logger: logger,
scopeFactory: const DefaultOrbitalScopeFactory(),
initialUri: Uri.parse('/'),
modules: [
OrbitalModule(
path: '/',
routes: [
OrbitalPageRoute(
path: '/',
builder: (context, routeContext) => const HomePage(),
),
],
),
],
),
);
What the bundle reexports #
- all public APIs from
orbital_core - all public APIs from
orbital_injector - all public APIs from
orbital_router enableOrbitalDevtools(...), a convenience wrapper aroundOrbitalDebugBridge.enable(...)
Design intent #
The bundle adds almost no new runtime behavior. Its value is ergonomic:
- single-import app bootstrapping
- aligned versions of the Orbital packages
- one obvious entrypoint for example apps and app-level tests
The underlying behavior still lives in the granular packages.
More detail #
See doc.md for package relationships, lifecycle flow and when to use the bundle versus granular imports.