@humanitec/autogen

Automatically generates type-safe TypeScript client code from Humanitec's OpenAPI specifications, producing fully-typed request/response interfaces, method signatures, and error handling boilerplate. The generator introspects the OpenAPI schema to emit strongly-typed classes and interfaces that map directly to API endpoints, eliminating manual client implementation and keeping generated code synchronized with API changes.

Provides auto-generated TypeScript method signatures that enforce type safety at compile-time for all Humanitec API operations, with built-in request validation and response deserialization. Each generated method maps to a specific API endpoint with typed parameters, return types, and error responses, enabling IDE autocomplete and catching type mismatches before runtime.

Packages the generated TypeScript client as a distributable npm module (@humanitec/autogen) that can be installed as a dependency in other projects, with semantic versioning and automatic updates when the Humanitec API schema changes. The package includes pre-compiled JavaScript, TypeScript source maps, and type definitions, enabling seamless integration into npm-based workflows.

Automatically handles conversion between JavaScript/TypeScript objects and HTTP request/response payloads, including JSON serialization, header management, and response parsing according to the OpenAPI schema. The generated client transparently converts typed method parameters into HTTP requests and parses responses back into typed objects, handling edge cases like nested objects, arrays, and optional fields.

Provides built-in support for Humanitec API authentication, handling credential injection into request headers and managing authentication state across multiple API calls. The generated client accepts authentication credentials (API keys, tokens) and automatically includes them in all outgoing requests without requiring manual header manipulation.

Automatically maps HTTP error responses to typed error objects that can be caught and handled in application code, with specific error types for different failure scenarios (4xx client errors, 5xx server errors, network failures). The generated client parses error responses according to the OpenAPI schema and throws typed exceptions that include status codes, error messages, and additional context.