Page MenuHomePhabricator

[EPIC] Should we transition Gruntfile.js tasks to NPM scripts in some projects?
Open, LowestPublicSpike

Description

Umbrella task for transitioning Gruntfile.js tasks into npm scripts in different projects.
A detailed template for the process: T246326: Process template: How to transition Gruntfile.js tasks to NPM scripts

With the decline of Grunt for many years now, it is unclear how long will it feasible to use it. The question is not whether to transition but when. The answer is different for projects and it can be many years. This task tracks the overall process and serves with examples and a template (T246326).

Projects

Other projects

Previous related tasks

T179195: Replace use of .eslintignore with ignore in Gruntfile.js in all repos, for consistency
T204176: Decide how to configure ESLint rules and ignores
T204260: Consolidate svgmin config and svg / grunt-svgmin checker

Related Objects

Event Timeline

Demian updated the task description. (Show Details)
Demian updated the task description. (Show Details)

Change 574636 had a related patch set uploaded (by Aron Manning; owner: Aron Manning):
[mediawiki/extensions/MultimediaViewer@master] Replace grunt tasks with npm scripts, remove unnecessary devDependencies.

https://gerrit.wikimedia.org/r/574636

Demian renamed this task from Transition Gruntfile.js tasks to NPM scripts to Transition Gruntfile.js tasks to NPM scripts (process template).Feb 27 2020, 9:33 AM
Demian updated the task description. (Show Details)
Demian renamed this task from Transition Gruntfile.js tasks to NPM scripts (process template) to Transition Gruntfile.js tasks to NPM scripts.Feb 27 2020, 9:39 AM
Demian updated the task description. (Show Details)

This needs to pass an RfC before implementing widely.

Jdlrobson added a subscriber: Jdlrobson.

@Demian - as far as I'm concerned only the reading web team has decided we dislike Gruntfile.js and to transition away from it. Grunt in general is still useful in many repos. I'd suggest reaching out to appropriate maintainers before writing patches for repos where these changes might not be wanted.

@Jdforrester-WMF is right when he says an RFC would be the route to go down here.

Jdlrobson renamed this task from Transition Gruntfile.js tasks to NPM scripts to [EPIC] Should we transition all Gruntfile.js tasks to NPM scripts ?.Mar 5 2020, 6:34 PM
Jdlrobson removed a subscriber: Jdlrobson.

@Demian - as far as I'm concerned only the reading web team has decided we dislike Gruntfile.js and to transition away from it.

I concur with your rename. I have no interest in transitioning projects that I don't know or work on. How would I know if it's beneficial...
The wording was misleading in that sense: it followed the commit comment practices, so thanks for finding a better expression for it.

My intent with this task and its subtasks was to document in one place the projects that do this transition and also to document the steps of the transition, to pass on the lessons learned.

Demian changed the subtype of this task from "Task" to "Spike".
Demian renamed this task from [EPIC] Should we transition all Gruntfile.js tasks to NPM scripts ? to [EPIC] Should we transition Gruntfile.js tasks to NPM scripts in some projects?.Jul 5 2020, 5:00 PM
Demian added a project: Spike.

Change 574636 had a related patch set uploaded (by Aron Manning; owner: Aron Manning):
[mediawiki/extensions/MultimediaViewer@master] [dev] Replace Grunt tasks with NPM scripts

https://gerrit.wikimedia.org/r/574636

Demian lowered the priority of this task from Low to Lowest.Nov 2 2020, 1:51 AM
Demian updated the task description. (Show Details)
Volker_E updated the task description. (Show Details)