Investigate the options available in the javascript library management
space and determine if using any existing system would allow results
similar to the results that we are aiming for in the PHP space. These
goals are broadly:
- To make managing the use of externally developed libraries easier by introducing a method to explicitly declare dependencies and their versions
- To promote expanding the use of code developed to support MediaWiki and the Wikimedia Foundation goals beyond the MediaWiki user community where the software has a broader use case than internal MediaWiki business logic
Ideally we would find a system that can be seamlessly integrated with Composer to provide a unified workflow for MW users.
A quick survey has found these possible options:
- npm + custom Composer integration
- bower + custom Composer integration
- [[ https://github.com/eloquent/composer-npm-bridge | composer-npm-bridge ]]
- [[ https://github.com/francoispluchino/composer-asset-plugin | composer-asset-plugin ]]
- [[ http://bowerphp.org/ | bowerphp ]] + custom Compser integration