vtex-io-render-runtime-and-blocks

To expose a React component as a VTEX IO Store block, you must register it in `store/interfaces.json` with a matching block ID and ensure the component mapping points to the actual React export. This enables theme configuration and storefront rendering.

A VTEX Store Framework block fails to render when its `store/interfaces.json` mapping is missing, the component value does not match a real React entry export, or theme block references are incorrect. Validating these mappings ensures proper block registration and rendering.

Configuring allowed child blocks in VTEX IO interfaces.json requires defining composition contracts and allowed settings that reflect runtime expectations. You must specify whether a block renders nested children or named block slots to ensure predictable block nesting behavior.

Block composition in the VTEX Store Framework is the mechanism defining how blocks render nested children versus named block slots. It uses `store/interfaces.json` to establish allowed child blocks, ensuring theme block nesting behaves predictably during storefront rendering.

Yes, VTEX IO Store Framework blocks require React because the framework maps block IDs from `store/interfaces.json` directly to real React entry exports. Without a React component export, theme configuration cannot resolve and the block will not render.

To fix missing interfaces.json mappings for VTEX storefront components, verify that every visible React component is declared with the correct block ID and component mapping. Ensure block IDs match theme usage and component fields resolve to real React entry exports.