vscode-azurefunctions
vscode-azurefunctions copied to clipboard
Fail to execute "Execute Function Now..." action after deploying the JavaScript V4 project to a Node.js 14 function app
OS: All Azure Resources extension: 20231114.1 Azure Functions Extension Version: v1.13.1 Regression: Not a regression
Repro Steps:
- Create a JavaScript V4 project and open in VS Code.
- Create a Node.js 14 function app -> Deploy the JavaScript V4 project to it -> Expand the function app -> Expand Functions -> Right click the function -> Click "Execute Function Now..." -> Fill default for the request body -> Enter.
- Check whether succeeds to execute "Execute Function Now..." action.
Expect: Succeed to execute "Execute Function Now..." action.
Actual:
Fail to execute "Execute Function Now..." action.
More Info:
- This issue also reproduces for the TypeScript V4 project.
- This issue doesn't reproduce after deploying the JavaScript V4 project to the function app created with other Node.js runtimes.
- This issue doesn't reproduce after deploying the JavaScript V3 project to the Node.js 14 function app.
Node v14 is ~EOL so we won't expect this to work going forward. We should revisit whether or not we should block users from creating function apps with this runtime.
This actually doesn't have anything to do with EOL dates. The old programming model (v3) is supported on Node.js v14+ and the new programming model (v4) is supported on Node.js v18+ as documented here. The new model has never and will never work on Node 14. The old model should continue to work regardless of the EOL date, although customers are required to upgrade before they receive customer support