@busflow/services
Status: Scaffold — not yet implemented
Purpose
Parent directory for isolated domain service packages. Each service is its own package with an independent package.json.
Principle: Runtime vs. Capability
A service package contains the capability (logic, templates, calculations). An app provides the runtime (HTTP endpoint, UI). The logic stays portable across consumers.
Services
| Service | Path | Consumers |
|---|---|---|
@busflow/services-wallet | wallet/ | booking-widget, passenger |
@busflow/services-notifications | notifications/ | workspace, driver, passenger |
@busflow/services-pricing | pricing/ | booking-widget, workspace |
@busflow/services-compliance | compliance/ | workspace, driver |
@busflow/services-pdf-parser | pdf-parser/ | workspace |
@busflow/services-accounting | accounting/ | workspace |
@busflow/services-routing | routing/ | driver, workspace |
See App Structure & Services for details.
Public API / Entrypoints
- Each child service owns its own
package.jsonand public entrypoint. - Parent directory is an index of service capabilities, not an importable runtime package.
Key Commands
- Run commands against the concrete child service package once implemented.
Related Docs
Common Pitfalls
- Do not couple service logic to a single app runtime.
- Keep templates, calculations, and adapters portable across web, worker, and CLI consumers.