Page MenuHomeMiraheze

Make sure npm works or create deploy repo for femiwiki
Closed, ResolvedPublic

Related Objects

StatusAssignedTask
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)
ResolvedUnknown Object (User)

Event Timeline

RhinosF1 created this task.
RhinosF1 added a subscriber: Unknown Object (User).Feb 21 2022, 12:19

@Universal_Omega: Can you create the repo? I can get it actually deployed.

Unknown Object (User) added a comment.Feb 21 2022, 18:02

@Universal_Omega: Can you create the repo? I can get it actually deployed.

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.

It shouldn't cause an issue. I can't really think of a better way.

RhinosF1 assigned this task to Unknown Object (User).Feb 23 2022, 10:27
RhinosF1 moved this task from Backlog to Short Term on the MediaWiki (SRE) board.
RhinosF1 raised the priority of this task from Low to High.EditedMar 2 2022, 20:19

Test deployment can be from 17th March

@Universal_Omega: status?

Unknown Object (User) added a comment.Mar 2 2022, 20:24

I'll try and get this done within the next few days (this week).

Reception123 lowered the priority of this task from High to Normal.Mar 3 2022, 07:10

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.

Unknown Object (User) moved this task from Backlog to Upgrade Blockers on the MediaWiki board.Mar 3 2022, 16:49
Unknown Object (User) added a project: Puppet.

What's the next steps here? And status?

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?

Unknown Object (User) added a comment.Apr 17 2022, 18:22

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.

You could vendor the dependencies by default.

You could vendor the dependencies by default.

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.

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.

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.

1: https://github.com/femiwiki/FemiwikiSkin/releases/latest

Unknown Object (User) added a parent task: T9163: Test all extensions for 1.38.
Unknown Object (User) closed this task as Resolved.Apr 30 2022, 06:20

This is now done.