Find the API for your task
Each package has an entry page and focused reference topics. Choose the responsibility first, then the API family. Complex packages have deeper navigation; small packages stay compact.
| Package | Responsibility | Topics |
|---|---|---|
| fetcher | HTTP requests | 6 |
| decorator | Declarative services | 3 |
| eventbus | Event delivery | 2 |
| eventstream | SSE consumption | 3 |
| storage | Stored values | 2 |
| openapi | OpenAPI type contracts | 3 |
| generator (5.x) | Generated clients | 5 |
| openai | Chat and token streams | 2 |
| cosec | Authentication and refresh | 3 |
| react | Component request state | 7 |
| wow (5.x) | Commands and queries | 9 |
| viewer (5.x, deprecated) | Data views and persistence | 8 |
Packages marked 5.x apply only to the 5.x line (npm 5.1.x, branch 5.x). From 6.0, Wow and the generator live in the Wow repository (wow.ahoo.me); their npm successors are @ahoo-wang/wow-client, @ahoo-wang/wow-react and @ahoo-wang/wow-generator (Wow 9.2.1 or later accepts fetcher 6). Viewer is frozen and superseded by @ahoo-wang/wow-view-engine, also on npm.
Use the right depth
Entry pages explain purpose, prerequisites, and topic choices; each package ends with a complete symbol index. Topic pages explain parameters, defaults, results, failures, and lifecycle. Use Guides for end-to-end work and Start for your first integration.
Reference follows current public exports and implementations. A source file inside a package does not imply a public package import.