In other recipes we only create config files if the bring additional value and don't only expose default variables and this looks only like the defaults 🤔

the http_client service needs to be explicitly enabled, this does it
but maybe we should enable it conditionally in the fwb integration!
Is that what your mean? Doing a class_exists check there and remove the recipe?

If the HttpClient package is not required by any of the skeleton's dependencies, it means it certainly can be activated automatically by the fwb if the package is installed, this would probably save a recipe for it 😄

Yes I thought about it. Does it makes sense?

I just added a comment on the PR that we should auto-activate it if the component is installed.