hyva-cms-components-dump

You can consolidate Hyvä CMS component definitions by running a PHP script from the Magento project root. It scans active modules across app/code and vendor paths, merging all components.json files into a single unified JSON object for review.

Merging Hyvä CMS components.json files works by scanning active Magento modules across app/code and vendor directories. It maps paths via etc/module.xml, preserving module load order to output a single unified JSON object containing all CMS component definitions.

Yes, you can detect missing or conflicting CMS component definitions in Magento by generating a consolidated JSON view. This unified output serves as a single source of truth to validate module component wiring and spot definition conflicts across modules.

Yes, you need to run the dump script from the Magento project root. This ensures the script can properly access and scan active modules across both app/code and vendor directories to successfully locate and merge Hyvä CMS components.

The best way to generate a single source of truth for Hyvä CMS component definitions is using a dump script that merges all components.json files from active Magento modules. It preserves module load order and outputs a unified JSON object for downstream analysis.