lldb-dap extension CI tests

[ashgti]

As we add more support to the vscode lldb-dap extension, it would be good to create some standard tests and CI checks for the vscode extension code.

Today, we're not checking things like if the package.json is valid or that npm run package is working as expected. They were broken recently by a bad merge and it was not caught by any CI jobs.

[llvmbot]

@llvm/issue-subscribers-lldb-dap

Author: John Harrison (ashgti)

As we add more support to the vscode lldb-dap extension, it would be good to create some standard tests and CI checks for the vscode extension code.

Today, we're not checking things like if the package.json is valid or that npm run package is working as expected. They were broken recently by a bad merge and it was not caught by any CI jobs.

[ashgti]

Its worth noting that there are multiple VSCode extensions in the llvm project.

• https://github.com/llvm/llvm-project/tree/main/mlir/utils/vscode
• https://github.com/llvm/llvm-project/tree/main/lldb/tools/lldb-dap
• https://github.com/llvm/llvm-project/tree/main/llvm/utils/vscode/llvm

Some consistency between these three may be helpful.

[da-viper]

is any of the other extensions currently tested in CI ?, as it would be easier to adapt it to the dap extension.

as I am not sure if the build dependencies such as npm/typescipt are in the build bot machines.