gchq/CyberChef

Packages which can't be updated easily

Open

#2 214 ouverte le 1 mars 2026

Voir sur GitHub
 (0 commentaires) (1 réaction) (0 assignés)JavaScript (3 944 forks)batch import
help wantedinfra/meta

Métriques du dépôt

Stars
 (34 843 stars)
Métriques de merge PR
 (Merge moyen 57j 13h) (62 PRs mergées en 30 j)

Description

This issue is for tracking those packages where a simple update is not possible, and the reason why.

The intent is simply to avoid wasting effort on retrying the non-trivial updates when doing a general dependencies cleanup.

PRs to address the "requires code change" cases are most welcome.

Please also add a comment if further cases are found.

Package Version Limit Reason
@xmldom/xmldom < 0.9.0 requires code change
bcryptjs < 3.0.0 requires code change
bootstrap < 5.0.0 requires code change
bson < 5.0.0 requires code change and tests fail with the most obvious/trivial changes
cbor < 10.0.0 requires newer node version
compression-webpack-plugin <12.0.0 requires node >= 20.9.0
copy-webpack-plugin <14.0.0 requires node: >= 20.9.0
cspell < 9.0.0 requires newer node version
eslint < 10.0.0 requires newer node version
eslint-plugin-jsdoc < 51.0.0 requires newer node version
fernet < 0.4.0 0.3.3 is actually a later release than 0.4.0
geodesy < 2.0.0 can't load js modules into an mjs file
jimp < 1.6.1 1.6.1 is a faulty release (see https://github.com/jimp-dev/jimp/issues/1402) and breaks everything! (hopefully any subsequent release will fix this)
jq-web < 0.6.0 fails when fetching wasm file (#2209)
jquery <4.0.0 clash with bootstrap peer dependency
otpauth < 9.4.0 requires newer node version
sitemap < 9.0.0 no longer provides default export - requires code change
uuid < 14.0.0 requires node >= 19 (expects crypto to be built in)
webpack-dev-server < 5.1.0 requires newer node version

Guide contributeur