Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | Unknown Object (User) | T9446 Upgrade to MediaWiki 1.39.1 | ||
Resolved | Unknown Object (User) | T8982 Migrate revision_actor_temp usage back to the revision table | ||
Resolved | Unknown Object (User) | T8743 Upgrade to MediaWiki 1.38.1 | ||
Resolved | Unknown Object (User) | T9163 Test all extensions for 1.38 | ||
Resolved | Unknown Object (User) | T8786 Make sure npm works or create deploy repo for femiwiki |
Event Timeline
I don't like the idea of a deploy repo for npm modules to use with a submodule. But if we really want to go here then sure, I can probably do that a bit later on.
Doing something for a 'test deployment' is by definition not high priority for me. Unless something absolutely needs to be done in the next few days because it is harming production I don't really see why it should be high priority.
I am curious why only femiwiki requires special additional steps. Is it because it is a skin? I guess some other extensions also require npm dependencies. Is there a thing to do for me, as a maintainer of the skin?
It's because NPM doesn't work due to us being IPV6, and GitHub being IPV4, so getting NPM dependencies from GitHub didn't work, it seems, from my understanding at least.
The tarball releases of the skin already vendor the dependencies. [1] In my opinion, downloading skin/extension by cloning as a submodule is not a usual case so I hope to try the solution only as of the last.
Is it means the below clause in package.json?
"dependencies": { "@femiwiki/ooui-femiwiki-theme": "https://github.com/femiwiki/OOUIFemiwikiTheme.git#main", "xeicon": "https://github.com/xpressengine/XEIcon.git#2.3.3" }
If in that case, I could publish the repository on NPM.