Node dependency update uses undefined version

[andrew-eldridge]

Severity

P3 - Medium (Minor functionality affected)

Describe the Bug with repro steps

Expected behavior:

• Node dependency is automatically updated on extension startup

Actual behavior:

• Version in Node url is 'vundefined' when downloading

What type of Logic App Is this happening in?

Standard (VSCode)

Are you experiencing a regression?

No response

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

Screenshots or Videos

Environment

• VS Code extension version: 5.230.15
• Bundle version: 1.156.11

Additional context

No response

[DaveSlinn]

This is a shot in the dark, as I don't know this code base at all, but I did try to analyze this problem because I'm having the same issue - during the runtime dependency validation, I see that same line

Downloading dependency from: https://nodejs.org/dist/vundefined/node-vundefined-win-x64.zip

Which of course is obviously wrong. According to the AI analysis, the function getLatestNodeJsVersion is passed a majorVersion parameter, which it believes comes from the nodejs value from this file:

https://cdn.functions.azure.com/public/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows/dependency.json

{
    "dotnet": "6,8",
    "funcCoreTools": "4",
    "nodejs": "18",
    "dotnetVersions": "6,8"
}

which is of the value "18". The function then loads json from github nodejs release endpoint:

export async function getLatestNodeJsVersion(context: IActionContext, majorVersion?: string): Promise<string> {
  context.telemetry.properties.nodeMajorVersion = majorVersion;

  if (majorVersion) {
    return await readJsonFromUrl('https://api.github.com/repos/nodejs/node/releases')
    ...

Which is returning 30 elements only, and currently, those values range from "v25.4.0" (the latest as of this message, released earlier today - Jan 19, 2026) to version "v24.3.0", released Jun 24, 2025.

Is it possible there are too many newer releases of Node so that it can't determine the latest version of node v18 to download. The getLatestNodeJsVersion function does not handle the case where no release matching the desired majorVersion, thereby leaving the return value as undefined. The subsequent call to getNodeJsBinariesReleaseUrl:

export function getNodeJsBinariesReleaseUrl(version: string, osPlatform: string, arch: string): string {
  if (osPlatform === 'win') {
    return `https://nodejs.org/dist/v${version}/node-v${version}-${osPlatform}-${arch}.zip`;
  }

  return `https://nodejs.org/dist/v${version}/node-v${version}-${osPlatform}-${arch}.tar.gz`;
}

results in https://nodejs.org/dist/vundefined/node-vundefined-win-x64.zip for me (win x64).

I looked up what the latest version of node 18 is, and it's 18.20.8, released March of 2025:

https://nodejs.org/dist/v18.20.8/node-v18.20.8-win-x64.zip

I manually downloaded and unzipped it, placed the files into my logic apps dependencies NodeJs folder:

C:\Users\{username}\.azurelogicapps\dependencies\NodeJs

** place it so that node.exe is in that folder along with the other files and a folder called node_modules.

After that, I restarted VS Code, opened the logic app workspace, and I was able to start both the designer and the data mapper without any more issues.

[devaraja666]

It may be a good idea to implement pagination, and loop through pages, collecting releases, until it find a match or there are no more pages.