tours module is rightly depending on the travel-demo module. This enables users to install travel-demo only, without having to install the tours module. The aim is to also showcase project and module setups.

However, page template home of travel-demo (see travel-demo/templates/pages/home.yaml) defines component availability of components that are only brought in by the tours module, such as:

areas:
  main:
    type: list
    availableComponents:
      tourCarousel:
        id: tours:components/tourCarousel
      tourTypeTeaserRow:
        id: tours:components/tourTypeTeaserRow
      # ...
      tourList:
        id: tours:components/tourList
      # ...

This results in an implicit circular dependency that needs to be resolved – even though it might not result in actual errors when adding components to that page (not yet tested).

Possible solution

Fix by using decoration.