vtex-io-app-contract

To define VTEX IO app contracts, you structure the manifest by specifying ownership, builders, dependencies, and peer dependencies. This governs identity, versioning, and scope to enable safe app composition across host environments.

Use dependencies for required internal packages, and peerDependencies when splitting contracts across multiple apps to ensure shared versions. This distinction enforces precise versioning and safe composition across editions and host environments.

The best way to scaffold a new VTEX IO app contract is using a minimal skeleton template. This validates manifest alignment and enforces governance rules for identity, builders, and billing options from the start.

Your VTEX IO app manifest needs builders and contract governance because defining boundaries without formal structure is error-prone. Governance ensures consistent ownership, scope, and versioning alignment with platform release processes.

Yes, you can split VTEX IO app contracts across multiple apps by using peerDependencies. This approach maintains precise identity and versioning rules while enabling safe composition across different editions and host environments.