-
Bug
-
Resolution: Fixed
-
Blocker
-
3.9.14, 3.9.19, 3.11.7, 3.11.12, 4.0.1, 4.0.6, 4.1, 4.1.1
Since September 2018 (MDL-63346):
- This policy will be applied to ALL supported branches, normal and security-only.
- This policy won't update any tool per se, unless strictly needed by nodejs/npm own dependencies/changes. It won't include npm audit changes either. Those are handled apart. So, normally, only changes to .nvmrc and package.json will happen. That will be achieved by:
- update .nvmrc to the new version.
- run nvm install && nvm alias default node && nvm use to install, set it as new default and use it for the next steps.
- update package.json and set engines to the new restriction (>= new version and < next major).
- When needed to bump components or run some audit, a new issue, similar to this, will be created and these steps performed in order to get a renewed npm-shrinkwrap.json file:
- remove node_modules & npm-shrinkwrap.json
- npm cache clear --force
- npm install
- npm shrinkwrap
- In any case, simple update or complete components bump, run grunt and verify that all the generated css/js/map stuff remains the same. If there are differences in the generation... it will need to be analysed and decided if:
- accepted (so everything, shrinkwrap and generated css/js/map) lands [or]
- not accepted (and only change .nvmrc and package.json) instead).
- The resulting branches will be sent to github (or similar), making a peer-review request here so both travis and cibot will verify that all them pass ok.
- Changes will be normally integrated and the NodeJSVersion template and NodeJSExactVersion templates will be updated with latest information in the Docs.
- TODO (MDLSITE-5536): A job @ CI servers will be, daily, using latest lts/current version to detect if there are npm-shrinkwrap.json changes. It will fail when that happens and inform integrators. Jumps to lts/next will be detected manually,.
This issue is being created because of this announcement about the end-of-life date for Node.js 16 (September 2023).
Node 18 is already stable and will become LTS on October 2022. Just before Moodle 4.1 release.
Another jump to the LTS (lts/hydrogen) will be needed then, though that one should be a smaller one than this one.
- caused a regression
-
MDL-77538 MDL-75012 seems to have broken all JavaScript on Windows
-
- Closed
-
-
MDL-77559 Revert NodeJS 18 bump (or significantly alter)
-
- Closed
-
-
MDL-77527 Upgrade to Node18 leads to different .map files in 39/311 branches
-
- Closed
-
- has a clone
-
MDL-79003 Bump NodeJS from lts/gallium to stable (>=v20.x.x), Take 2
-
- Closed
-
- has a non-specific relationship to
-
MDL-73144 Allow use of dartsass for scss compilation
-
- Closed
-
- is a clone of
-
MDL-73915 Bump NodeJS version, dependencies, and update JS build process, drop IE support
-
- Closed
-
- will help resolve
-
MDL-77083 github archive checksums no longer match for custom npm dependencies shifter and istanbul
-
- Closed
-