WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #51603, comment 18


Ignore:
Timestamp:
11/26/2020 08:27:28 AM (5 months ago)
Author:
netweb
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #51603, comment 18

    v1 v2  
    2929To not have to done any "archaeology" gear, we should update all the supported branches 3.7 thru 5.6 to use Node.js v14.x and NPM v7.x
    3030
    31 To do this, for WP 3.8 `grunt-cssjanus` package would be replaced with the same RTL CSS package used in `/trunk` `grunt-rtlcss`, this brings the RTL CSS improvements over CSSJanus to the users still using WP 3.8. For WP 3.9, `grunt-sass` would be updated from `0.8.0` to `3.1.0` and the latest Dart Sass instead of LibSass/Node-Sass
     31To do this, for WP 3.8 `grunt-cssjanus` package would be replaced with the same RTL CSS package used in `/trunk` `grunt-rtlcss`, this brings the RTL CSS improvements over CSSJanus to the users still using WP 3.8. For WP 3.9, `grunt-sass` would be updated from `0.8.0` to `3.1.0` and the latest Dart Sass instead of LibSass/Node-Sass (see also #51763 Evaluate moving to Dart Sass)
    3232
    3333Likewise for any other Node.js packages, if the old WordPress branch uses an old version of a package it can be upgraded to the latest, or changed to what is now used in `/trunk` where new and improved packages have been chosen (E.g. The switch to RTLCSS from CSSJanus)
     
    3636
    3737Even the `@wordpress/scripts` package can be added to the WordPress 3.7 branches, going forward when `/trunk` updates packages in `package.json`, these changes are backported to the branches thru 3.7 where appropriate.
     38
     39It will aid backporting the local docker environment in #48301, and backporting GitHub Actions in #50401 too including future maintenance of these environments in the legacy branches
    3840
    3941Further, every supported branch of WordPress 3.7 thru 5.6 and beyond will have these features: