Build your application

Choose the task you need to complete. New to Fetcher? Start with a runnable result first.

• HTTP requests: A Fetch-capable runtime and the core package. Run the local HTTP example before connecting an application API.
• Service clients: Use direct Fetcher calls for a few endpoints. Decorators require a compatible TypeScript compiler; generation requires a complete OpenAPI document and a compile step. Neither creates backend routes.
• Streaming data: Your runtime needs Fetch, Response bodies, and ReadableStream. The server must emit SSE frames; a normal JSON response is not an event stream. Keep a caller-owned cancellation signal for long-lived reads.
• React data flow: Start in an existing React application with the declared peer dependencies. The runnable React example supplies a deterministic backend fixture; production routes remain application-owned.
• View Engine: Build a shadcn/Base UI record page with component-configuration persistence, built-in filters/cells and explicit ViewHost services. Start with the workspace example.
• Ant Design Viewer (maintenance mode, deprecated): Start with local data in a React application with Viewer peers. View displays one view; Viewer also manages a view collection. Your data adapter applies queries and owns persistence.
• Platform integrations: Wow and CoSec require compatible server protocols, authentication and application-specific routes. Storage and local events can be used without a platform server. Confirm the chosen package peers before installing.

For a working baseline use complete examples. For ownership and adoption tradeoffs use architecture.