Table of Contents & Menu
On this page
Navigation

CI/CD Hyvä Installation

The app/etc/hyva-themes.json file defines which modules are included when generating a theme's styles.css.

For details on automatic tailwind.config.js merging, refer to the "Module tailwind.config.js merging" documentation.

Hyvä 1.1.14 and newer

For Hyvä 1.1.14+, the app/etc/hyva-themes.json file is automatically generated after running any of these commands:

  • bin/magento setup:install
  • bin/magento setup:upgrade
  • bin/magento module:enable
  • bin/magento module:disable

This automation typically covers all scenarios, eliminating manual concerns during CI/CD builds.

Note on Hyvä 1.1.14 (Magento 2.4.7+)

For Hyvä 1.1.14 on Magento 2.4.7 or newer, a command might be required after installing a compatibility module. However, as of Hyvä 1.1.15, this process is generally automated by the commands listed above.

Previously, before automatic tailwind.config.js merging, themes needed manual purge content configuration. Now, no manual configuration changes are required.

Hyvä 1.1.13 and older

For Hyvä 1.1.13 and older, the app/etc/hyva-themes.json file is automatically generated after these commands:

  • bin/magento setup:upgrade
  • bin/magento module:enable
  • bin/magento module:disable

However, `bin/magento setup:install` does *not* generate `hyva-themes.json` in these older versions.

Therefore, if you run bin/magento setup:install when Hyvä packages are already installed, you *must* run the command bin/magento hyva:config:generate afterward. Do this before you generate the styles.css during your build.

This scenario is common in CI/CD builds.