Add Node.js version validation for HTML package builds

[Copilot]

Add Node.js version validation for HTML package builds

This PR implements validation to ensure the installed Node.js version is compatible with the target MES version when building HTML packages.

Changes

• NodeVersionUtilities: Detects installed Node.js version via node --version and validates compatibility against required version from DependencyVersionService

• Error messages: Added NodeNotInstalled and IncompatibleNodeVersion with links to installation documentation

• Handler validation: Both HtmlNgCliPackageTypeHandler and HtmlGulpPackageTypeHandler now validate Node.js version in constructor before build steps execute (with null safety checks for test compatibility)

• Tests: Coverage for version detection and validation logic across MES versions

Example

With Node.js v18 installed, attempting to build an MES 11 HTML package now fails early with:

Node.js version 18.19.0 is not compatible with MES version 11.0.0. 
This MES version requires Node.js v20.x. 
See https://criticalmanufacturing.github.io/cli/01-install/#nodejs-and-npm for version compatibility.

Updates

• ✅ Rebased with development branch (commit 2a35457)
• ✅ Fixed commit messages to follow conventional commit format
• ✅ Squashed commits into feat commits
• ✅ Fixed NullReferenceException in tests by adding null checks for ExecutionContext

Original prompt

---

This section details on the original issue you should resolve

<issue_title>cmf build html should throw an exception if node is not compatible</issue_title>
<issue_description>when running cmf build for html packages we should throw an exception if the node version is not compatible with the targe MES version.
https://criticalmanufacturing.github.io/cli/01-install/#nodejs-and-npm</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes cmf build html should throw an exception if node is not compatible #444

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[joaoopereira]

@m-s- @pedroapap please review. It looks good to me

[joaoopereira]

@copilot rebase with development. and please follow our commit guidelines

[Copilot]

@copilot rebase with development. and please follow our commit guidelines

Rebased with development branch (cea36c60) and reformatted commits to follow conventional commit guidelines:

• Changed "Add Node.js version validation for HTML packages" → feat: add Node.js version validation for HTML package builds
• Changed "Add tests for Node.js version validation" → squashed into main commit
• Removed "Initial plan" empty commit

The branch is now based on the latest development commit (2e60db9) with a single properly formatted conventional commit.

[joaoopereira]

@copilot tests are throwing Object reference not set to an instance of an object.

[Copilot]

@copilot tests are throwing Object reference not set to an instance of an object.

Fixed in cdcf40b. The NullReferenceException occurred because the HTML handlers were accessing ExecutionContext.Instance.ProjectConfig and ExecutionContext.ServiceProvider in their constructors without null checks. During test execution, these aren't always initialized.

Added null safety checks to both HtmlNgCliPackageTypeHandler and HtmlGulpPackageTypeHandler - the Node.js validation now only runs when ExecutionContext is properly initialized, allowing tests to construct handler instances without errors.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 0t3vsblobprodcus362.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 1javsblobprodcus364.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 2zrvsblobprodcus388.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 37bvsblobprodcus311.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 4m6vsblobprodcus384.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 4zjvsblobprodcus390.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 51yvsblobprodcus36.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• 5dkvsblobprodcus355.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• c78vsblobprodcus322.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• h6tvsblobprodcus346.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• jd4vsblobprodcus366.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• kh4vsblobprodcus325.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• kxqvsblobprodcus376.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• l49vsblobprodcus358.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• mfjvsblobprodcus373.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• p2ovsblobprodcus312.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• s8mvsblobprodcus38.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• se1vsblobprodcus349.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• uy6vsblobprodcus34.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)
• x3yvsblobprodcus370.vsblob.vsassets.io
  • Triggering command: /usr/bin/dotnet dotnet test --filter FullyQualifiedName~NodeVersionUtilities --verbosity normal (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)