Sub-package install functionality will work by specifying the drupal-libraries-dependencies extra option. It may be set to true or an array of package names, the array name approach isn't recursive, so each package name must be explicitly declared.
Also added quality of life improvements such as an alternative configuration definition for supporting different file extensions, SHA1 checksum verification and removing example/demo/test files from the libraries (see PSA-2011-002).
With regards to the lock file, it stores the installed state of the libraries inside a local installed-libraries.json file inside the drupal-libraries-installer vendor folder similar to how composer itself does it.
It was done this way to keep compatibility with the old API which works only on the post-install and post-update hooks, and at that point the lock file has already been written to.
Addresses #1 and #2.
Sub-package install functionality will work by specifying the
drupal-libraries-dependencies
extra option. It may be set totrue
or an array of package names, the array name approach isn't recursive, so each package name must be explicitly declared.Also added quality of life improvements such as an alternative configuration definition for supporting different file extensions, SHA1 checksum verification and removing example/demo/test files from the libraries (see PSA-2011-002).
With regards to the lock file, it stores the installed state of the libraries inside a local
installed-libraries.json
file inside thedrupal-libraries-installer
vendor folder similar to howcomposer
itself does it. It was done this way to keep compatibility with the old API which works only on thepost-install
andpost-update
hooks, and at that point the lock file has already been written to.