Repository navigation
Consider updates to NPM packages / dependencies #314
Description
These are the installed versions of dependencies, and the currently available dependencies.
@types/mark.js ^8.11.8 → ^8.11.12
eslint ^8.54.0 → ^9.29.0
eslint-plugin-security ^1.7.1 → ^3.0.1
express ^4.17.2 → ^5.1.0
fs-extra ^10.0.0 → ^11.3.0
glob ^10.3.10 → ^11.0.3
node-fetch ^2.0 → ^3.3
openai ^4.24.1 → ^5.8.2
prismjs ^1.26.0 → ^1.30.0
rimraf ^3.0.2 → ^6.0.1
Are there any specfic reasons to avoid upgrading any of these?
I won't submit a PR with a mass update but I will try to update some in my own environment to see how they work with this doc package.
Except for PrismJS I'm using all of those deps in other projects at the current versions.
Activity
TonyGravagno commentedon Jun 27, 2025
Notes:
devDeps all updated, no issues.
Updated deps in the following order, no issues:
prismjs <=1.29.0
Severity: high
Cross-site Scripting in Prism - GHSA-3949-f494-cm99
PrismJS DOM Clobbering vulnerability - GHSA-x7hr-w5r2-h6wg
Did a final "npm up" to update sub-dependencies Ref #312
Final "npx npm-check-updates"
This all looks good to me. The project builds with every change and of course on completion.
I'm submitting a PR.