Currently, I am working on a language server extension for vs-code that is based on the lsp-sample code. You can find the code here: https://github.com/microsoft/vscode-extension-samples/tree/master/lsp-sample
My challenge lies in WebPacking the extension before publishing it. Unfortunately, I have not been able to generate any functional output. The issue stems from the fact that the process keeps reporting an error message stating "Starting client failed", which upon further investigation, indicates that the server portion of the extension is failing to start.
I believe the problem may be related to how I am packaging the server component. However, given my limited experience with WebPack, I am unsure of what else I can attempt to resolve this issue.
An inquiry was posted on the vs-code-extension repository regarding this matter, but unfortunately, no responses have been received thus far. You can view the open issue here: https://github.com/microsoft/vscode-extension-samples/issues/191
To simplify the troubleshooting process and avoid confusion caused by project-specific details, I have created a fork of the lsp-sample code containing only the relevant code snippets that I am trying to troubleshoot. This fork is accessible here: https://github.com/obiwanjacobi/vscode-extension-samples/tree/191-webpack-issue/lsp-sample
Essentially, my approach involves running two separate WebPack processes - one for the client side of the extension that operates within vscode, and another for the server portion of my language server (which should be reusable). Each of these WebPack setups includes a webpack.config.js file as well as a package.json script entry to execute them.