How to update JavaScript components
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	JanZerebecki
	Apr 22 2016, 2:02 PM

Description

How to update JavaScript components? As it is useful to use JavaScript components in MediaWiki core and Extensions, how do we update them from the upstream repository (e.g. using npm)? For sending the JS to the client usually minification or something equivalent is required at some point in time between update and sending out the response to the client. Then ideally all this is automated. This has some similarities for the same question for PHP components, see T105638 for that.

Related Objects

Mentioned In: T133462: Provide standard-compatible way to load multi-file packages (not plain concatenation)
T133026: [Bug] WDQS GUI caching
Mentioned Here: T107561: MediaWiki support for Composer equivalent for JavaScript packages
T105638: RFC: Streamlining Composer usage

Event Timeline

JanZerebecki created this task.Apr 22 2016, 2:02 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 22 2016, 2:02 PM

JanZerebecki mentioned this in T133026: [Bug] WDQS GUI caching.Apr 22 2016, 4:12 PM

JanZerebecki added a project: Front-end-Standards-Group.Apr 23 2016, 5:18 PM

JanZerebecki updated the task description. (Show Details)

• brion subscribed.Apr 23 2016, 7:29 PM

Ricordisamoa subscribed.Apr 23 2016, 10:33 PM

• RobLa-WMF mentioned this in Unknown Object (Event).Apr 27 2016, 6:28 AM

A cautionary tale about relying too much on npm, composer & co: http://blog.npmjs.org/post/141577284765/kik-left-pad-and-npm

I'm all for using package managers. But we have to make sure we get the workflow right, and don't end up depending on a single point of failure that we don't even control.

@JanZerebecki do you plan to propose a solution in this RFC, or do you want to have a completely open field narrowing or even problem definition session? As of now, there doesn't seem to be much to discuss here.