Repository navigation
docs: state that newer Node.js major versions are not supported - #6627
Draft
totally-not-ai[bot] wants to merge 6 commits into
Draft
totally-not-ai[bot] wants to merge 6 commits into
totally-not-ai[bot] wants to merge 6 commits into
Conversation
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.
Contributor
|
This pull request targets If the change applies only to this release, remove the label. |
Contributor
Preview DeploymentThis PR has been deployed for preview. URL: https://docs-preview-pr-6627.fly.dev Changed pagesAdded content is highlighted in green; removed content is marked in red on each page.
Base branch changesNot 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
prepare-frontendgoal description, the Gradle plugin pages and the upgrading guides use the same wording.node.folderwhatever its version, so it's the way to run a newer major version at your own risk. The npm requirements note mentionsnode.folderas well. The version comparison table lists Node 24 for Vaadin 25.Test summary
node.folderhandling, 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