Change Details

As in T206069, this task encompasses the work to start transitioning Gruntfile.js tasks to package.json. This task covers all simple transitions such as ESLint and creating tasks for what remains. Delete any relevant dependencies as you go and see [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Popups/+/master/package.json#3 | Popups for reference ]]. = Developer notes [] eslint is not using grunt [] stylelint is not using grunt [] banana-checker is not using grunt [] grunt is removed from codebase = Motivation Via T206069: * Relying on Grunt plugin maintainers (e.g. dependant on grunt eslint-plugin upgrades everytime eslint is upgraded. Working now, albeit slower pace, but no guarantee it will in future) * Grunt going out of fashion * Focus should be on production code and less on tooling * Only package.json to npm install, npm start * Understanding how Grunt works is an unnecessary and additional tax developers need to make when working with our codebases and it's not clear if it's worth it. * Tasks can be run in package.json. Grunt not needed for that purpose. * CI faster as no longer needs to download grunt and grunt plugins.

As in T206069, this task encompasses the work to start transitioning Gruntfile.js tasks to package.json. This task covers all simple transitions such as ESLint and creating tasks for what remains. Delete any relevant dependencies as you go and see [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Popups/+/master/package.json#3 | Popups for reference ]]. = Developer notes [x] eslint is not using grunt [x] stylelint is not using grunt [x] banana-checker is not using grunt [x] grunt is removed from codebase = Motivation Via T206069: * Relying on Grunt plugin maintainers (e.g. dependant on grunt eslint-plugin upgrades everytime eslint is upgraded. Working now, albeit slower pace, but no guarantee it will in future) * Grunt going out of fashion * Focus should be on production code and less on tooling * Only package.json to npm install, npm start * Understanding how Grunt works is an unnecessary and additional tax developers need to make when working with our codebases and it's not clear if it's worth it. * Tasks can be run in package.json. Grunt not needed for that purpose. * CI faster as no longer needs to download grunt and grunt plugins.

As in T206069, this task encompasses the work to start transitioning Gruntfile.js tasks to package.json. This task covers all simple transitions such as ESLint and creating tasks for what remains. Delete any relevant dependencies as you go and see [[ https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Popups/+/master/package.json#3 | Popups for reference ]]. = Developer notes [x] eslint is not using grunt [x] stylelint is not using grunt [x] banana-checker is not using grunt [x] grunt is removed from codebase = Motivation Via T206069: * Relying on Grunt plugin maintainers (e.g. dependant on grunt eslint-plugin upgrades everytime eslint is upgraded. Working now, albeit slower pace, but no guarantee it will in future) * Grunt going out of fashion * Focus should be on production code and less on tooling * Only package.json to npm install, npm start * Understanding how Grunt works is an unnecessary and additional tax developers need to make when working with our codebases and it's not clear if it's worth it. * Tasks can be run in package.json. Grunt not needed for that purpose. * CI faster as no longer needs to download grunt and grunt plugins.