User tests: Successful: Unsuccessful:
Updates npm build-tooling dependencies and resolves all npm audit findings.
npm audit fix resolved 9 vulnerabilities (browserslist, deepmerge-ts/html-to-text/mailparser chain, fast-uri, mysql2, postcss-selector-parser, qs, @humanfs/node) — transitive or in-range, no manual changes needed.esbuild 0.27.7 → 0.28.2, fixing GHSA-g7r4-m6w7-qqqr (arbitrary file read via esbuild's dev server on Windows). Flagged as a semver-major bump by npm, but the changelog shows only install-script/tooling changes, not JS API changes.tinymce 8.8.2 → 8.9.0, choices.js 11.2.1 → 11.2.4, sa11y 4.4.1 → 5.0.9 (major), and the full @codemirror/* family (autocomplete, commands, lang-html, lang-markdown, language, lint, search, state, view) to their latest in-range versions.Each package was reviewed individually against its actual usage in this repo (not just changelog headlines) before updating — no breaking changes intersect with how Joomla consumes any of them. Full details/verdicts per package are documented separately.
No PHP/JS source changes; only package.json, package-lock.json, and plugins/editors/tinymce/tinymce.xml (its <version> is written automatically by the plg_editors_tinymce build task to match the bundled TinyMCE version).
npm install (this also triggers a full production build via this repo's install script).npm audit — expect 0 vulnerabilities.npm run build:dev -- -a or npm run build -- -a — expect exit code 0, all build tasks green, no new errors (pre-existing Sass/Bootstrap deprecation warnings are unrelated).plg_system_jooa11y): load a front-end page with ?jooa11y=1, confirm the panel and tooltips render correctly.npm audit reports 10 vulnerabilities (2 low, 2 moderate, 6 high). tinymce, choices.js, sa11y, and the @codemirror/* packages are behind their latest available versions.
npm audit reports 0 vulnerabilities. All reviewed packages are updated to their latest available (in-range, or reviewed-and-bumped-range for sa11y) versions, with no functional regressions in the TinyMCE editor, CodeMirror editor, fancy-select fields, or accessibility checker.
Please select:
| Status | New | ⇒ | Pending |
| Category | ⇒ | NPM Change Front End Plugins |
| Title |
|
||||||
I‘ve used this when doing the updates for 5.4.0: https://www.npmjs.com/package/npm-check-updates
Installed it and then ncu -i --format group
I‘ve used this when doing the updates for 5.4.0: https://www.npmjs.com/package/npm-check-updates
Installed it and then ncu -i --format group.
Patch updates can be always done, minor updates should be checked ( release notes), and with major updates it needs to be very careful.
I‘ve used this when doing the updates for 5.4.0: https://www.npmjs.com/package/npm-check-updates
I‘ve used this when doing the updates for 5.4.0: https://www.npmjs.com/package/npm-check-updates
Installed it and then ncu -I —format group.
I‘ve used this when doing the updates for 5.4.0: https://www.npmjs.com/package/npm-check-updates
Installed it and then ncu -i —format group.
I‘ve used this when doing the updates for 5.4.0: https://www.npmjs.com/package/npm-check-updates
Installed it and then ncu -i —format group.
| Title |
|
||||||
this does resolve audit reported scripts but still leaves very many outdated scripts that we should really update. At a minimum that would be all the scripts in red