Skip to content

Usage

Start with common-http for website requests, provider endpoints and internal HTTP services. Its guide covers construction, configuration, execution, authentication integration and transport lifecycle. Compose it with common-auth for supplied credentials, token keepers, encrypted custody, OAuth login and incoming application verification. Use common-browser for browser contexts, actions, observations and typed extraction; provider workflows compose above these mechanics.

PackageCurrent responsibility and status
common-httpImplemented async HTTP client, contracts, configuration, reports and transports
common-executionReleased execution foundation consumed from the existing common repository
common-coreReleased core primitives consumed from the existing common repository
common-authImplemented credentials, authentication, token custody, OAuth login, signing and verification
common-ratesReserved for shared quota coordination
common-browserBrowser runtime, contexts, actions, observations, typed extraction and explicit resource ownership
common-reportsReport documents (builder, email/interactive/Ghost renderers, plots) and provider-neutral email over SMTP, the Gmail API and Microsoft Graph

Reserved directories do not imply completed implementations. Use the owning package’s release and migration records when choosing a distribution. Auth’s HTTP extra requires common-http 0.2. Each consumer imports only the packages it needs; the workspace root is not installed as a runtime dependency.