integration-builder

To scaffold a provider integration package, run the integration-builder to generate a complete npm workspace structure under packages/<provider-package>/ with package.json, tsconfig.json, and src/ files. You get a ready-to-implement package with integration definitions, DI setup, and adapters.

Scaffolding integration adapters generates core files including package.json, tsconfig.json, src/, integration.ts, and di.ts. The package structure also includes module metadata, ACL definitions, and blueprints for health checks, i18n assets, widgets, and unit tests.

Yes, the integration scaffolding handles webhook processing and i18n setup by providing blueprints for both within the generated package. It includes localization assets and webhook processing modules alongside adapters, credentials handling, and health checks.

Yes, you can use this to add Stripe or DHL integrations. When adding new external integrations for payments, shipping, data sync, communication, or storage, it scaffolds a complete provider package ready for implementation with all required conventional structures.

The best way to enforce consistent project structure is through automated scaffolding that generates standardized provider integration packages. It enforces a conventional package structure under packages/, exports integration definitions, and registers adapters via dependency injection.

Yes, unit tests are included when generating a provider integration package. The scaffolding provides a test blueprint alongside adapter modules, i18n assets, and health checks, ensuring the generated package is ready for wired implementation into the marketplace.