Skip to content

Conversation

@Artur-
Copy link
Member

@Artur- Artur- commented Jan 7, 2026

Adds a nodeFolder configuration option to specify custom node installation directory. This directory is always used if specified

For #23119

Artur- added 2 commits January 7, 2026 16:27
…NodeResolver

- Add nodeFolder configuration option to specify custom node installation directory
- Consolidate duplicate node/npm resolution logic into reusable methods
- Extract normalizeVersion() helper to eliminate duplicate version normalization
- Add findNpmCliScript() to unify npm-cli.js lookup across all resolution paths
- Add tryResolveFromExecutable() as generic resolution method
- Remove redundant getGlobalNpmCliScript(), getCustomFolderNpmCliScript(), getNpmCliScriptPath()
- Reduce code duplication by ~50-60 lines

This improves maintainability and makes it easier to add new node resolution strategies in the future.
@github-actions
Copy link

github-actions bot commented Jan 7, 2026

Test Results

1 307 files  ± 0  1 307 suites  ±0   1h 16m 16s ⏱️ + 2m 2s
9 269 tests ± 0  9 201 ✅ ± 0  68 💤 ±0  0 ❌ ±0 
9 717 runs   - 10  9 641 ✅  - 10  76 💤 ±0  0 ❌ ±0 

Results for commit f1865f3. ± Comparison against base commit 127c92c.

♻️ This comment has been updated with latest results.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 8, 2026

@caalador caalador added the target/25.0 Cherry-pick to 25.0 branch label Jan 8, 2026
@Artur- Artur- merged commit 4b4b6be into main Jan 8, 2026
49 of 50 checks passed
@Artur- Artur- deleted the custom-node-folder branch January 8, 2026 09:11
vaadin-bot pushed a commit that referenced this pull request Jan 8, 2026
Adds a `nodeFolder` configuration option to specify custom node installation directory. This directory is always used if specified

For #23119
vaadin-bot added a commit that referenced this pull request Jan 8, 2026
)

Adds a `nodeFolder` configuration option to specify custom node installation directory. This directory is always used if specified

For #23119

Co-authored-by: Artur Signell <[email protected]>
@mcollovati
Copy link
Collaborator

Unfortunately, late on the party here. I guess the new property should be added also as @InputParameter to the PrepareFrontendInputProperties to make it work with Gradle configuration cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants