Video.js is available on packagist/composer, so rather than keeping copies of the files in our local repo, would be nice to bring them in...
Obviously, as it's not PHP, and the file path isn't going to be fixed, this is going to be more complicated...
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T150128 Bring video.js in via composer | |||
| Declined | None | T150129 Find location of Composer files |
Change 320094 had a related patch set uploaded (by Reedy):
[WIP] Bring in video.js from composer
That is the point, I'm making that commit now. It won't be such a simple swap over as it would be for PHP files, so might need a bit of playing about
Change 320095 had a related patch set uploaded (by Reedy):
Add videojs/video.js for TimedMediaHandler
I don't think we should pull this from composer. The general direction we are looking in is npm and maybe yarn. pulling this one library into composer doesn't help us much and will create further disjunction.
I'd rather just commit the node_modules subdirectory.
Looks kinda unloved... https://github.com/wikimedia/mediawiki-extensions-TimedMediaHandler/blob/master/package.json#L17 - 5.12.2 exists in our repo...
Related discussion about JS frontend library management is in T107561: MediaWiki support for Composer equivalent for JavaScript packages.