Problem/Motivation
Dropping the support for [Libraries API] module
as the following was committed in Drupal 8.9.x branch and it will be in Drupal 9.x branch too
https://git.drupalcode.org/project/drupal/commit/1edf15f
#3110305: Drupal 8.9.x deprecation signposting
#3096648: Add support for third party libraries in site specific and install profile specific libraries folders
Add to that No new releases for Libraries API since 8.x-3.0-alpha1 released 27 January 2018
Moving our logic to use the same logic as in the Drupal core 8.9.x
Support for third party libraries in site specific and install profile specific libraries folders
https://www.drupal.org/node/3099614
In Drupal 8, contrib modules use the Libraries module to allow project to store third party libraries in different locations. There locations are:
- PATH/TO/SITE/libraries (for example sites/example.com)
- libraries
- PATH/TO/INSTALL_PROFILE/libraries
This functionality has been move to Drupal core and now libraries with locations starting with
/libraries/
can be in any of these locations. They are searched in the order above and the first match found is used.
Proposed resolution
Remove the Libraries API module
As much of its functionality had been moved to core
We had that in
#3114086: Drop support for [Libraries API] module. And move the logic to Drupal core 8.9.x libraries finding way
Remaining tasks
Check all logic on needed modules.
User interface changes
N/A
API changes
Change of the scanning logic to the better Drupal 9 scanning for libraries
Data model changes
N/A
Comments
Comment #3
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #4
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #5
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #6
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commentedComment #7
Rajab Natshah CreditAttribution: Rajab Natshah at Vardot for Vardot commented