Action fails on Node 24 default runner: "(0 , util_1.isNullOrUndefined) is not a function

Open
#166 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
azure, github-actions, node.js, typescript
Domain
ci-cd, cloud, devops

Research direction

Start by reproducing the action startup failure on a Node 24 GitHub-hosted runner with the load test configuration shown. Inspect the action's bundled dependencies for the removed util.isNullOrUndefined call, then verify the action runs successfully with the listed standard configuration on Node 24. Done means both v1.2.1 and v1.2.5 failure paths are addressed without requiring the Node 20 workaround.

Written by the indexing model from the issue text.

Description

Describe the bug

The action crashes with a TypeError when GitHub Actions runners default to Node 24,
which is now the standard runtime since GitHub's Node 20 deprecation rollout.

Error:
Error: (0 , util_1.isNullOrUndefined) is not a function

This happens because util.isNullOrUndefined was removed in Node 24, and the
action's bundled dependencies still call it.

To Reproduce

  1. Use a GitHub Actions runner defaulting to Node 24 (current default as of mid-2026)

  2. Run the action with a standard load test config:

    • name: Run Azure Load Test
      uses: azure/load-testing@v1.2.5
      with:
      loadTestConfigFile: loadtest-config.yaml
      loadTestResource:
      resourceGroup:
      waitForCompletion: true
      env:
      USRNAME: ***
      PASSWORD: ***
      TEST_ID_CONFIG:

  3. Observe the crash immediately on action startup

Expected behavior

The action should run successfully on Node 24, matching the runner's default.

Workaround

Setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true in the step's env forces
the runner back to Node 20, which avoids the crash — but this is only a temporary
option since GitHub is fully removing Node 20 support later in 2026:
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Versions tested
  • v1.2.1 — fails
  • v1.2.5 (latest) — fails identically
Environment
  • GitHub-hosted runner (ubuntu-latest)
  • Node 24 (runner default)
Image Image
Dominant language
TypeScript
Stars
20
Forks
27
Avg merge
6d 16h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/load-testing

All issues in Azure/load-testing

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.