Dirk Fauth

@msujew I tried but it doesn't change anything. It still shows this: ``` yarn install v1.22.19 $ node-gyp install gyp info it worked if it ends with ok gyp info...

@paul-marechal I followed the instructions already, and I have installed the Visual Studio Build Tools manually and not via npm. Actually I also clearly stated the problem. I have installed...

> To add insult to the injury, yarn seems to pick a random node-gyp version instead of the hoisted [email protected] Not sure if this is really random. If I execute...

@paul-marechal Thanks a lot for your support! > If I understand correctly you need to set a few environment variables That was the missing part indeed. I configured the proxy...

Today I tried to create a Theia based application as described here https://theia-ide.org/docs/composing_applications/ Having only Visual Studio 2022 installed it is impossible to build. Again the node-gyp version issue. But...

I followed the [Build your own IDE/Tool](https://theia-ide.org/docs/composing_applications/) tutorial and added the dev dependency: ``` { "private": true, "dependencies": { "@theia/callhierarchy": "next", "@theia/file-search": "next", "@theia/git": "next", "@theia/markers": "next", "@theia/messages": "next", "@theia/mini-browser":...

@msujew Hm, well I am using the package.json that is shown in the documentation which is using the `next` version. I suppose that means 1.2.17 if I understand the content...

@msujew How would I then update to the latest version? Only by deleting the .lock files etc.? Actually not necessary as I started over and over the last weeks as...

@rotty3000 Did you have time to investigate on this? IIUC it should work. Atomos is providing an example that shows a similar approach with an executable jar using Spring Loader...

@xeraph thanks for fixing this. I tested it and it works as intended for the artefacts from Maven Central. Eclipse is re-bundling the artefact from Maven to add jar signing....