@intersystems/intersystems-iris-native package seems to cause VS Code extension host process to crash on Windows

[gjsjohnmurray]

I have developed a VS Code extension called gj :: configExplorer

• Extension on Marketplace, currently packaged so it cannot be installed on Windows because of this issue.
• DC article with video
• Open Exchange package entered in current DC contest

As is typical of VS Code extensions mine is written in Typescript and uses the @intersystems/intersystems-iris-native package which InterSystems recently published on npmjs.com (current version 2.0.2).

It works fine when VS Code's extension host (EH) process is executing on Linux. But when the EH is on Windows activation of my extension (by clicking on the 'Explore Configuration' button that it adds to Server Manager entries) immediately crashes the EH. VS Code restarts the EH three times before concluding that the problem wasn't a glitch. Thereafter no extensions work in VS Code until it is restarted.

VS Code is built on Electron and I found this note about a requirement that a native Node module must comply with in order to work on Windows.

I will be happy to work with InterSystems to investigate this.

[gjsjohnmurray]

microsoft/vscode#248331 (comment) is an example of another extension crashing EH, where the cause was traced to this.

[gjsjohnmurray]

Raised with WRC as #1004732

[gjsjohnmurray]

Update from WRC:

You are right about win_delay_load_hook module

Fix incoming:

DP-445929 -- GGD214 - Including win_delay_load_hook.cc as part of the build

The updated library should be released in the upcoming weeks. It should be version 2.0.3