Failed to configure Bridge to Kubernetes: No debug configurations found in launch.json to run the app locally

[MaxiPalle]

Proceeded as in https://code.visualstudio.com/docs/containers/bridge-to-kubernetes. With npm install I receive the following warnings:

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.2.13
npm WARN contoso.bikerental.bikes@0.1.0 No repository field.
npm WARN contoso.bikerental.bikes@0.1.0 No license field.

When now trying to run "Bridge to Kubernetes: Configure", I receive the following error message:

Failed to configure Bridge to Kubernetes: No debug configurations found in launch.json to run the app locally_

[amsoedal]

Hi @MaxiPalle, thanks for reaching out to us. Which app are you trying to debug? The samples from this repo (e.g. BikeSharingApp/Bikes) should all have debug configurations in launch.json already, like this one:

{
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch via NPM",
            "runtimeExecutable": "npm",
            "runtimeArgs": [
                "run-script",
                "debug"
            ],
            "port": 9229
        }
    ]
}

The error you're seeing means that Bridge wasn't able to find a debug configuration in the local folder. Do you have the Bikes folder open in VSCode, or perhaps a more top-level folder?

Hope this helps!

[MaxiPalle]

I have opened the 'BikeSharingApp/Bikes' folder. launch.json with above mentioned code can be found in subfolder .vscode.

[daniv-msft]

Thank you for your reply. I tested this scenario but unfortunately couldn't reproduce the issue. Could you please confirm that you're using the latest version of the https://github.com/microsoft/mindaro repository, and that the folder opened in VS Code is <YOUR_PATH>\mindaro-master\samples\BikeSharingApp\Bikes? Also, are you just opening this Bikes folder or are you opening multiple folders as a multi-root workspace?

Finally, if the issue keeps reproducing, could you please attach to this issue the logs from our VS Code extension?

• Open VS Code.
• Reproduce the issue.
• Open the Bridge to Kubernetes Output window to see the path of our logs:
• Close VS Code.
• Attach the logs to this issue.

Alternatively, as these logs might contain personally identifiable information, if you don't feel comfortable posting them publicly on GitHub you can also send them by email to BridgeToKubernetes@microsoft.com. Thank you for reporting this issue!