Docker image Debian 12 Bookworm, Nodejs 24+, clean up deprecated dependencies

[nerun]

Dockerfile

• switched to node:bookworm and removed NODE_OPTIONS workaround

New image node:bookworm (Debian 12) uses Nodejs v24.3.0 on 08 jul 2025, the old one, node:buster (Debian 10) uses Nodejs 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 the ENV NODE_OPTIONS=--openssl-legacy-provider line from Dockerfile.

package.json

• Removed gatsby-plugin-remove-trailing-slashes

This package has been deprecated. Author message:

This plugin's functionality is now built-in to Gatsby. Use the trailingSlash feature: https://gatsby.dev/trailing-slash. This package will no longer receive updates.

trailingSlash support was added in gatsby@4.7.0. The package.json sets ^4.0.2 which installs gatsby@4.25.9 (npm ls gatsby).

• Updated gatsby-plugin-algolia: 0.19.0 → 1.0.3, it was too old, many incompatibilities

gatsby-config.js

• removed gatsby-plugin-remove-trailing-slashes (read above)
• added trailingSlashes (read above):

module.exports = {
    trailingSlash: 'never',
    // ... outher settings
};

package-lock.json

• Regenerated

README

Correct invalid git clone URL:

from:

git clone git@github.com:hasura/gatsby-gitbook-starter.git

to:

git clone https://github.com/hasura/gatsby-gitbook-starter.git`

[nerun]

Addresses issue #261

[nerun]

@abhinav-hasura, could you please take a look at this? Sorry for the inconvenience, I know it's almost abandoned.