Docker image Debian 12 Bookworm, Nodejs 24+, clean up deprecated dependencies #262
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dockerfile
node:bookworm
and removedNODE_OPTIONS
workaroundNew image
node:bookworm
(Debian 12) usesNodejs v24.3.0
on 08 jul 2025, the old one,node:buster
(Debian 10) usesNodejs v20.8.1
. Debian 10 was too old.Starting with Node.js 20.0.0, the
--openssl-legacy-provider
flag is no longer needed, as the runtime includes improved compatibility with OpenSSL 3.0 by default. This flag was only necessary in versions 17 through 19 to support legacy cryptographic algorithms. If you're using Node.js 20 or later, it's safe and recommended to remove theENV NODE_OPTIONS=--openssl-legacy-provider
line from Dockerfile.package.json
This package has been deprecated. Author message:
trailingSlash
support was added ingatsby@4.7.0
. Thepackage.json
sets^4.0.2
which installsgatsby@4.25.9
(npm ls gatsby).gatsby-plugin-algolia
:0.19.0
→1.0.3
, it was too old, many incompatibilitiesgatsby-config.js
package-lock.json
README
Correct invalid git clone URL:
from:
to: