Package Catalog
@figentra/contracts
Shared TypeScript interfaces and type contracts used across every service in your monorepo.
@figentra/health
Health check utilities for HTTP services, including readiness and liveness probe handlers.
@figentra/container
A lightweight dependency injection container for wiring up services without heavy frameworks.
@figentra/testing
Test utilities, reusable fixtures, and setup helpers that make writing integration tests faster.
@figentra/error
Standardized, typed error classes and handling utilities for consistent error propagation.
@figentra/config
Environment variable parsing and validation so misconfigured services fail fast at startup.
@figentra/logger
Structured JSON logging with configurable log levels and context-aware child loggers.
@figentra/validation
Input validation backed by typed schemas, returning structured error details on failure.
Package Stability
Use this table to understand which packages are production-ready and which are still evolving.
Stable packages follow strict semver and will not introduce breaking changes in a minor or patch release. Beta packages may still have API surface changes in minor releases — pin these versions tightly until they graduate.
Installation
Install the packages your service needs by adding them to itspackage.json. The example below installs the three most commonly used packages together.
Keep all
@figentra/* packages at the same version across your monorepo. Mismatched versions can cause subtle type incompatibilities and runtime inconsistencies, particularly when shared contracts are involved. Use your package manager’s workspace features or a tool like Syncpack to enforce version alignment.