Update Node.js to >= 24.0 and Yarn to 4.18.1 for Varbase Components

Problem/Motivation

Node.js 20 reached end of life on 30 April 2026, and Drupal core main now requires "node": ">= 24.0" in core/package.json. Varbase Components still pins Node 20 in its engines and GitLab CI.

Node 24 is the LTS line, latest v24.22.2, and it is one of the lines the November 2026 security releases will patch. Pinning the major picks those patches up with no further change.

Steps to reproduce

1. On 4.0.x and 3.1.x, open package.json: the engines say "node": ">= 20.0".
2. Open .gitlab-ci.yml: the browser job installs NodeSource setup_20.x. On 3.1.x, .gitlab-ci-local.yml runs node:20.

Proposed resolution

• package.json engines: "node": ">= 24.0". Yarn moves to yarn@4.18.1 with the floor ">= 4.18.1", and .yarnrc.yml follows the Varbase standard (approvedGitRepositories, enableScripts, nodeLinker: node-modules, npmMinimalAgeGate: 0), which Yarn before 4.14.0 rejects.
• .gitlab-ci.yml: NodeSource setup_24.x. .gitlab-ci-local.yml on 3.1.x: node:24.
• yarn.lock re-resolved to the newest versions the existing ranges allow. No range in package.json changes.

AI-Generated: Yes

Remaining tasks

• ✅ File an issue
• ✅ Addition/Change/Update/Fix
• ✅ Testing to ensure no regression
• ➖ Automated unit testing coverage
• ➖ Automated functional testing coverage
• ➖ UX/UI designer responsibilities
• ➖ Readability
• ➖ Accessibility
• ➖ Performance
• ➖ Security
• ➖ Developer Documentation
• ➖ User Guide Documentation
• ❌ Reviewed by human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Release notes snippet
• ✅ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• Node.js 24 or newer is now required, in the engines and CI. Node 20 is end of life.