Skip to main content
The egg supports eight Node.js versions, each provided by the parkervcp/yolks image collection. You select a Docker image from the Docker Image dropdown on your server’s Startup tab in the panel.
You can change the Docker image at any time from your server’s Startup settings in the panel. Restart the server after switching to apply the change.

Available Images

Node.js VersionDocker Image
Node.js 25 (Latest)ghcr.io/parkervcp/yolks:nodejs_25
Node.js 24 (LTS)ghcr.io/parkervcp/yolks:nodejs_24
Node.js 23ghcr.io/parkervcp/yolks:nodejs_23
Node.js 22 (LTS)ghcr.io/parkervcp/yolks:nodejs_22
Node.js 21ghcr.io/parkervcp/yolks:nodejs_21
Node.js 20 (LTS)ghcr.io/parkervcp/yolks:nodejs_20
Node.js 19ghcr.io/parkervcp/yolks:nodejs_19
Node.js 18 (LTS)ghcr.io/parkervcp/yolks:nodejs_18

Choosing a Version

LTS versions are recommended for most deployments. Long-Term Support releases receive security patches and bug fixes for an extended period, making them the safest choice for production servers. The current LTS versions available in this egg are Node.js 18, 20, 22, and 24. Use the latest non-LTS release (currently Node.js 25) only if your application explicitly requires features not yet available in an LTS version. Non-LTS releases reach end-of-life faster and may introduce breaking changes.
Next.js itself has its own minimum Node.js requirement. Check your version of Next.js against the official Next.js documentation to confirm compatibility before selecting an older image such as Node.js 18.

LTS Release Schedule

Node.js releases follow a predictable cadence: even-numbered versions become LTS, odd-numbered versions do not. If you want long-term stability without frequent image changes, stick to the even-numbered LTS images.
ImageLTSRecommended Use
Node.js 25NoBleeding-edge features only
Node.js 24YesLatest stable LTS
Node.js 23NoShort-term testing
Node.js 22YesStable, widely supported
Node.js 21NoShort-term testing
Node.js 20YesStable, widely supported
Node.js 19NoLegacy
Node.js 18YesLegacy LTS