@sashainparis, if I understand the output correctly, this error will be fixed...

@sashainparis, if I understand the output correctly, this error will be fixed if the patch we have in #2 is committed.

The Composer facade is using the .info.yml file to build the dependency graph and that is incorrect right now and the patch fixes that. Once the patch is committed, the d.o packager will update the generated composer.json as well.

Either way, I don't have strong opinions on having composer.json or not. I am just saying that I have seen it drift from the module's actual requirements before and hence I avoid it unless it is required. Here, I don't think it is required. We just need to commit the patch and also probably create a release.