Known Issue : Running Nodejs services locally fails with Azure Function Core Tools 4.2.1 and 4.2.2

This issue was discovered during testing of the latest version of BaaS. This is due to a change in Azure Function Core Tools that affects versions 2025.09, 2025.10 and 2025.11 of Backend as a Service.

Issue description:

After upgrading Azure Function Core Tools from version 4.1.2 to higher versions (4.2.1 and 4.2.2 at the time of writing), running and debugging Nodejs BaaS services locally in Visual Studio Code fails.

Workaround:
Install version 4.1.2 using the command

npm i -g azure-functions-core-tools@4 .1.2 --unsafe-perm true

Find more posts tagged with

Comments

Abhinav Katta

For people copy-pasting the command, there is an extra space in the version number, please correct it as follows 😊

npm i -g azure-functions-core-tools@4.1.2 --unsafe-perm true

Mia Klein Huge

Thanks for catching that Abhinav! I've edited out the extra space in the original post.

Peter Grew

In the BaaS Health Check log you will see two entries of Azure Function Core Tools

The "AzureCoreTools" entry show the installed version number regardless of installation method.
The "AzureCoreToolsNPM" entry show the version number for the npm installed version only.
NPM install is required by BaaS, so this entry should have a version number.
Now "AzureCoreToolsNPM" shows the latest available version instead of installed version.
This is corrected in the 2025.11 release.

Mia Klein Huge

This issue has been reported to Azure, and the root cause is identified:

Start Debugging fails to launch · Issue #4663 · Azure/azure-functions-core-tools
As of release 2025.12 of Infor BaaS, the effects of the changed behavior is mitigated, and the described workaround is not needed.

Copyright © 2025 Infor. All rights reserved.