- 🇬🇧United Kingdom catch
Closing as duplicate of ✨ Implement core management of 3rd-party FE libraries Active
More and more modules have npm dependencies. Installing such dependencies require manual changes (in composer.json) or using unsupported solutions (like asset-packagist).
These solutions are wrong for various reasons
- hard to define
- hard to install
- hard to update
- and might be insecure
asset-packagist:
Many distributions use asset-packagist:
Lightning →
,
Varbase →
Steps to configure asset-packagist
Problems:
- asset-packagist seems unmaintained
- npm packages should not be managed with composer
#3198245: Composer script: enable-asset-packagist →
example solutions requiring manual changes:
project dependency visualizer complicated install, currently using unmaintained library
project chosen complicated install, currently using unofficial, deprecated library
copy-files-from-to manually defined assets, no relation to Drupal projects
Problems:
- need to inform and educate the user about the installation
- the configuration is not user friendly, and can lead to issues
- manual changes required to update the package, which might result using insecure release
Develop an official npm package management solution for Drupal, which is as good and easy to use as composer.
Discuss the solution, create child issues.
---
Closed: duplicate
11.0 🔥
Affects the content, performance, or handling of Javascript.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Closing as duplicate of ✨ Implement core management of 3rd-party FE libraries Active