Token module as a requirement when installing ECA

Thanks @rodmarasi for your request.

Token support is already available in Drupal core and in ECA, even without the contrib token module. What that module provides, is some extra functionality, which is completely optional. One extra feature from that module is the token browser, but that's not essential.

ECA as it is published today has no other dependency than Drupal core. That has been a deliberate design decision and we want to keep it like that.

Yes, the token module is valuable, and it's recommended to use it, but it won't become a dependency for ECA. Especially because ECA in production will often being used without any UI and then the need for the token module is even less.

Hope you can follow that decision?

Well, ECA is just a processor that works in the background. All the visible stuff is not required to do all that. When you e.g. build and configure all your models in a development and/or test stage, you can then deploy all those models as configuration entities to your live site where ECA is doing its work with them. But you can turn off all UI components, i.e. the modeller modules and ECA UI, when you don't want anyone to fiddle around with the models in production. I know, not everyone will actually do that, but some customers will certainly prefer that.

This is very similar to views, fields, menus and a couple of other Drupal core modules as well: they have their functionality in their main modules and they all come with companion UI modules, that can be disabled, when not required. For high performance sites, this can be a significant benefit on live sites.