Don't worry about it. Node's file not found messages are kind of hard to parse, they regularly throw me off for a moment as well.

Well, uhm, read the error message and look for that file it's complaining about.

Doesn't look like it, the Windows SDK seems to be missing. I added a proper error message for that case.

It reads the registry to find out things about your Visual Studio installation. Do you have that installed?

Ah, looks like it's some issue which has been resolved after the last Kode Studio release then. Well, will be fixed in the next one.

OK, I'm sure you're looking forward to a little debugging session. You can use vscode, install the Kha extension pack, then get the vscode-krom-debug repository, open it in vscode and start debugging.

Try to set the Krom path to just kromlocation.

Nope. Also not sure anything but Windows still uses hardware cursors but maybe you can help me out getting up to date on the current state of affairs.

Adobe sold Air, like, a week ago? Also I see no use for it with Kha, the flash/air runtime is way slower than all the other targets and the GPU features are from 20 years ago. It made sense as a fallback for Internet Explorer <= 8 (the JS runtime in IE9 already seriously outperformed flash) and for debugging back when Haxe only really supported debugging via flash - but that's it IMHO.
The Node target also isn't updated regularly - also it's probably not what you think it is, it runs applications in headless mode for Kha's prototypical network multiplayer support.

The Unity target is outdated since we have real console targets and I think about just throwing it away. Will have a look at that Flash error though (don't really care about that one anymore either though).
With native IDE I mean Android Studio for Android, Visual Studio for Windows,... - the usual workflow is to develop using the html5 or Krom debugger in Kode Studio, then export to the "native IDE" for your target systems and run it in those to see what's going on if anything doesn't work.