Error: Eleventy requires Node.js version =14 – Eleventy 2.x CLI on Node 12

Question

Determine whether Eleventy 2.x should replace the hard Node.js version error with a warning when run on Node 12, allowing a smoother upgrade path for legacy environments.

The underlying Eleventy code uses ES2020 features unavailable in Node 12, so a warning may still lead to later runtime failures; the trade‑off between developer convenience and build reliability needs clarification.

Would issuing a warning instead of an error improve migration experience without compromising build reliability? What fallback mechanisms could inform users of impending incompatibility while still permitting the CLI to start?

Tasadduq Burney · Answer

Answer
Eleventy 2.x should keep the hard error; issuing a warning would not prevent runtime failures because the CLI relies on ES2020 syntax unavailable in Node 12.
Likely explanation
The Eleventy 2.x CLI uses optional chaining, nullish coalescing and other ECMAScript 2020 features that Node 12 does not implement, so the code would throw syntax errors if executed.
Confirmed fact
The package.json for @11ty/eleventy declares "engines": { "node": ">=14" }, causing npm/yarn to block installation on Node 12.
Steps to resolve

Check the current Node version: node -v
If the version is below v14, upgrade Node (e.g., nvm install 14 or nvm use 14, or download the installer from nodejs.org).
Reinstall Eleventy locally: npm install @11ty/eleventy@latest (or delete node_modules and run npm install).

Only if you have a specific reason to run Eleventy on Node 12 (e.g., a locked CI image) should you consider using Eleventy 1.x, which supports Node 10+, but you will miss newer features and bug fixes.

Error: Eleventy requires Node.js version >=14 – Eleventy 2.x CLI on Node 12

1 answer

0 question comments

Answer

Likely explanation

Confirmed fact

Steps to resolve

Your perspective belongs here.