Topic on Module talk:ExtensionJson

This JSON contains references to non-existent composer packages in composer field, probably coming from the extensions composer.json or package.json. Example: Admin_links. Perhaps, some checks should be made.Alexander Mashin ^talk 05:05, 20 July 2024 (UTC)

I wonder if maybe those extensions should be changed not to have a package name if it doesnt exist.

Yeah, it seems the best fix is for Composer names that aren't registered to be removed from the extensions' composer.json files. (Or for them to be registered, of course.)

There are some I think (the Bluespice ones?) that are valid names for a private Composer registry, so I'm not sure how those are supposed to be handled. Although looking now I can't find any documentation about that. Lots of the Bluespice extensions seem to have unregistered Composer names.

I think quite a few extension authors put "name": "mediawiki/foo" thinking that it's the thing to do, despite not being able to register anything within the mediawiki Packagist namespace.

I, on the other hand, suggest that something like composer show be called for any extension claiming to be a Composer package while the JSON is assembled.

Hoping that many extension maintainers rectify the issue goodwise will not lead anywhere.
Alexander Mashin ^talk 15:20, 20 July 2024 (UTC)

Good idea. I've opened phab:T370729.

But I still think the composer.json files should be actually fixed to not include the invalid names, or for the maintainers to register them on Packagist. :-)

@Alex Mashin: Code is fixed and deployed, and the next update should remove the non-existent Composer packages.

Thank you, now this .json will become even more useful.
Alexander Mashin ^talk 02:06, 25 July 2024 (UTC)

Actually I got it wrong, and there's a follow up patch. But then it'll work! :)

Okay, fixed now!