You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Breaking changes to JavaScript Debug Configuration
2
+
3
+
The debug configuration for v2 of the Azure Functions runtime [has changed](https://github.com/Azure/azure-functions-core-tools/issues/521) and old configurations will likely fail with the error "Cannot connect to runtime process, timeout after 10000 ms". You will automatically be prompted to update your configuration when you open a project. However, you can manually update your project with one of the following options:
4
+
5
+
The first option is to add `languageWorkers:node:arguments` to your `runFunctionsHost` task in `.vscode\tasks.json` as seen below:
1. Add the `FUNCTIONS_WORKER_RUNTIME` setting to your `local.settings.json`:
88
+
89
+
```json
90
+
{
91
+
"IsEncrypted": false,
92
+
"Values": {
93
+
"AzureWebJobsStorage": "",
94
+
"FUNCTIONS_WORKER_RUNTIME": "node"
95
+
}
96
+
}
97
+
```
98
+
99
+
The recommended debug configuration going forward has not been finalized. It will likely be similar to Option 2, but without a change to `local.settings.json` (since that file is not tracked by git). See [here](https://github.com/Azure/azure-functions-host/issues/3120) for more information.
Copy file name to clipboardExpand all lines: package.nls.json
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,7 @@
33
33
"azFunc.showCoreToolsWarningDescription": "Show a warning if your installed version of Azure Functions Core Tools is out-of-date.",
34
34
"azFunc.show64BitWarningDescription": "Show a warning to install a 64-bit version of the Azure Functions Core Tools when you create a .NET Framework project.",
35
35
"azFunc.showProjectWarningDescription": "Show a warning when an Azure Functions project was detected that has not been initialized for use in VS Code.",
36
+
"azFunc.showDebugConfigWarningDescription": "Show a warning when an Azure Functions project was detected that has an out-of-date debug configuration.",
@@ -24,6 +30,8 @@ export async function validateFunctionProjects(actionContext: IActionContext, ui
24
30
25
31
if(isInitializedProject(folderPath)){
26
32
actionContext.properties.isInitialized='true';
33
+
actionContext.suppressErrorDisplay=true;// Swallow errors when verifying debug config. No point in showing an error if we can't understand the project anyways
* JavaScript debugging in the func cli had breaking changes in v2.0.1-beta.30. This verifies users are up-to-date with the latest working debug config.
constresult: vscode.MessageItem|undefined=awaitvscode.window.showInformationMessage(localize('tasksUpdated','Your "tasks.json" file has been updated.'),viewFile);
constmessage: string=localize('uninitializedWarning','Your debug configuration is out of date and may not work with the latest version of the Azure Functions Core Tools.');
0 commit comments