Add the external library as a requirement to composer.json

This requires the 0.7.x-dev version right now because I messed up the 0.7.22 release. I hope we can fix that later.

jan kellermann → made their first commit to this issue’s fork.

Maybe just tag with 0.7.22.1? I think better than -dev.

I would like only to "suggest" because user's may choose for their own. We for example use whitelisting for drupal/*-projects on https://repo.packagist.org to load primary from packages.drupal.org. And we use automatic audits for sources and want to keep the dependency to the github project ("SBOM").

I added also documentation.

Thank you very much, @jurgenhaas!
The changes are merged. If there is a new version constraint without -dev please reopen this ticket.

As mentioned on Slack, what about the idea of tagging the JS library with 3.0.0 so that it becomes obvious that it's related to this module's main version? It would be feasible also because it is in fact a different version from upstream as it comes with a composer.json with a different namespace and a Drupal related type attribute.

What do you think?

@jan kellermann The library is now available as 3.0.0 and only contains the required files, not the development related ones. I've updated the requirement in a new MR, please have a look.

Thank you! Great that dev files are not included.
Merged :)

Automatically closed - issue fixed for 2 weeks with no activity.