Skip to content

Version incompatibility for Azure Functions Core Tools blocks execution of swa start #970

Open

Description

Are you accessing the CLI from the default port :4280 ?

  • No, I am using a different port number (--port) and accessing the CLI from that port
  • Yes, I am accessing the CLI from port :4280

Describe the bug
Working in ubuntu on the latest version of node and the swa cli, adding managed apis causes the cli to no longer work in terms of starting the app because of a version incompatability being registered between node and the azure functions core tools.

✖ Found Azure Functions Core Tools v4 which is incompatible with your current Node.js v24.5.0.
✖ See https://aka.ms/functions-node-versions for more information.

To Reproduce
Steps to reproduce the behavior:

  1. Install node
> node --version
v24.5.0
  1. Install swa
> swa --version
2.0.6
  1. In an swa project, create a dotnet8 isolated function runtime (could work with others but this is what I used)
  2. Make sure to add your ap directory to your swa cli config
  3. Run swa start triggering core tools grab and then error due to version incompatability```

swa start
✖ Found Azure Functions Core Tools v4 which is incompatible with your current Node.js v24.5.0.
✖ See https://aka.ms/functions-node-versions for more information.



**Expected behavior**
`swa start` should work OR I should be able to disable parts of the project from being booted up to get around these sorts of errors.



**Desktop (please complete the following information):**

- Ubuntu 24.04

Activity

  1. stephlocke commented on Aug 7, 2025

    @stephlocke
    Author

    PR #971 submitted as this errors only the swa cli side and has no upstream resolution requirements

  2. cjk7989 commented on Aug 14, 2025

    @cjk7989
    Contributor

    Hi Steph Locke (@stephlocke), SWA haven't supported deploying node 24 APIs, see https://learn.microsoft.com/en-us/azure/static-web-apps/languages-runtimes. We recommand to temporarily apply this change to the local branch, if you want to execute "swa start" to run node 24 sites, Appoligize for the inconvenience.

  3. unowiz commented on Aug 14, 2025

    @unowiz

    Steph Locke (@stephlocke) I've the same problem and I switched to use node 22. Check this #791 (comment)

    The cli seems to restricts itself to lts version

    export function isCoreToolsVersionCompatible(coreToolsVersion, nodeVersion) {
        // Runtime support reference: https://docs.microsoft.com/azure/azure-functions/functions-versions?pivots=programming-language-javascript#languages
        switch (coreToolsVersion) {
            case 4:
                return nodeVersion >= 18 && nodeVersion <= 22;
            case 3:
                return nodeVersion >= 14 && nodeVersion <= 20;
            case 2:
                return nodeVersion >= 10 && nodeVersion <= 14;
            default:
                return false;
        }
    }
  4. scottrudy commented on Nov 15, 2025

    @scottrudy

    Bump: Node 24 is LTS and the PR has been sitting since August. Azure Functions have supported Node 24 LTS in Preview as well since Ignite. Any updates on 2.0.8?

    https://github.com/Azure/azure-functions-nodejs-library/wiki/2025-Roadmap
    Azure/azure-functions-nodejs-library#360

  5. cjk7989 commented on Jan 26, 2026

    @cjk7989
    Contributor

    Scott (@scottrudy) thank you for your suggestion.

    We are rolling out Node.js 22 support for Static Web Apps this week. Regarding Node.js 24, Static Web Apps uses Oryx for build operations, and the current Bullseye-based images do not yet support Node 24. We are actively coordinating with the Oryx team to confirm availability of a compatible image version.

    Once the Oryx team confirms image availability, we will implement Node 24 support within two weeks from that confirmation. We will keep you updated on the progress.

  6. scottrudy commented on Jan 27, 2026

    @scottrudy
  7. Shuvra17 commented on Jun 22, 2026

    @Shuvra17

    Thanks for working on this issue. We’re currently facing : Azure Functions Core Tools v4 is not compatible with newer Node versions (v22/v24), which is impacting our local SWA development and build flows.
    Could you please provide any indication of when this issue is likely to be resolved or when support for newer Node versions might be available?
    Also, in the meantime, is there any recommended workaround (other than downgrading Node to v20) that would allow us to continue using newer Node versions?
    Appreciate your guidance.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions