Error during deployment ~0.5 : remote: No available node.js version matches application's constraint of >=6.4.0

Repro steps

1. Using Azure Function ~0.5
2. Having a package.json having "engines": { "node": ">=6.4.0" }
3. Deploying a Node.js v6.4.0 Azure Fonction with git

Expected behavior

Node.js v6.4.0 should be on the server as 0.5 release note says :

Moved to Node.js 6.4.0

Actual behavior

Error during deployment

remote: Looking for app.js/server.js under site root.
remote: Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0.
remote: An error has occurred during web site deployment.
remote: select node version failed
remote: Missing server.js/app.js files, web.config is not generated
remote: No available node.js version matches application's version constraint of '>=6.4.0'. Use package.json to choose one of the available versions.
remote: 
remote: Error - Changes committed to remote repository but deployment to website failed.

Known workarounds

Actually using Node.js v6.3.0 in my package.json

"engines": {
  "node": ">=6.3.0"
}

iisnode.yml will be nodeProcessCommandLine: "D:\Program Files (x86)\nodejs\6.3.0\node.exe"

Related information

• Programming language used : Node.js v6.4.0
• Application Settings : WEBSITE_NODE_DEFAULT_VERSION = 4.1.2 (wtf?)

[davidebbo]

We now have Node v6.5 available, which should address the original issue.

[VishalGulati]

done… please reference the issue here : #792