Skip to content

docs: state that newer Node.js major versions are not supported - #6627

Draft
totally-not-ai[bot] wants to merge 6 commits into
v25.3from
claude/v25.3-node-max-version
Draft

totally-not-ai[bot] wants to merge 6 commits into
v25.3from
claude/v25.3-node-max-version

Conversation

@totally-not-ai

@totally-not-ai totally-not-ai Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Vaadin uses a globally installed Node.js only when its major version is supported, and it skips a global Node.js whose major version is newer than that, just like one that is too old. It then installs its own Node.js into ~/.vaadin, which also fails when the build machine can't reach the download server. The docs said "Node.js 24 or later" and recommended the latest LTS version, so readers on a newer Node.js didn't expect this.

What changed

  • Supported Technologies lists Node.js 24 and says that later major versions aren't supported. The page now describes supported versions rather than minimum versions.
  • The Node.js page recommends a supported major version instead of the latest LTS, and its resolution order says that a global Node.js that's too old or too new is skipped.
  • The prepare-frontend goal description, the Gradle plugin pages and the upgrading guides use the same wording.
  • The Node.js page says that Vaadin uses the Node.js in node.folder whatever its version, so it's the way to run a newer major version at your own risk. The npm requirements note mentions node.folder as well. The version comparison table lists Node 24 for Vaadin 25.

Test summary

  • Checked the statements, including the node.folder handling, against the Node.js resolution in Flow 25.3 (supported major version 24, global Node.js outside the range is skipped).

Working on behalf of Olli

Vaadin uses a globally installed Node.js only when its major version is
within the supported range. A newer major version is skipped like a too
old one, and Vaadin installs its own Node.js into ~/.vaadin instead.
The compatibility page said "24 or later", and the Node.js page
recommended the latest LTS version, which is now outside that range.
@github-actions

Copy link
Copy Markdown
Contributor

This pull request targets v25.3, a release branch. A change made only there is lost when the next release branch is cut from main. This pull request is therefore labeled target/main: after it's merged, a bot cherry-picks it to main.

If the change applies only to this release, remove the label.

@github-actions github-actions Bot added the target/main cherry pick to main branch label Nov 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Preview Deployment

This PR has been deployed for preview.

URL: https://docs-preview-pr-6627.fly.dev

Changed pages

Added content is highlighted in green; removed content is marked in red on each page.

Base branch changes

Not marked in the preview: v25.3 is a maintenance branch, not a stacked pull request branch. Everything highlighted in the preview belongs to this PR.

Built from 90cc48e

@totally-not-ai
totally-not-ai Bot requested a review from Legioth November 11, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

target/main cherry pick to main branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants