Jan Kaniewski

It's a warning, I believe it's been there in socket.io plugin for a while (has to do with json conversion), not sure of root cause

Do we have a dump or stack trace available for a crash?

You're missing dependencies: 1) The actual node executable, if you look at e.g. https://github.com/getnamo/nodejs-ue4/releases/tag/0.5.0, download the *nodejs-ue4.24-v0.5.0.7z* for example, you can extract ```Source/ThirdParty``` into ```{project root}/Plugins/nodejs-ue4/Source/ThirdParty``` to add the thirdparty...

Added https://github.com/getnamo/nodejs-ue4/blob/master/README.md#using-git-instead-of-releases readme section with link to the third party dependencies here: https://github.com/getnamo/nodejs-ue4/releases/download/0.5.0/nodejs-v0.5.0git-thirdparty-dependencies-only.7z That should make using the plugin with a fresh git pull a bit simpler.

The node_modules are included in the zip, so no npm i should be required when using that zip (untested though)

What does the log say? this is where the wrapper script starts, you may want to trace it from there to see where it could be crashing: https://github.com/getnamo/nodejs-ue4/blob/master/Content/Scripts/nodeWrapper.js#L101

It won't work on Android, currently implemented as a windows only architecture due to using a separate node.exe instance ( windows specific code is in https://github.com/getnamo/nodejs-ue4/blob/master/Source/CommandLine/Private/NodeCmd.cpp#L300). Same idea could likely...

It's from https://nodejs.org/en/download/, pick e.g. Windows Binary(.zip) 64bit and drag and drop e.g. ```node-v16.13.0-win-x64``` renaming it to ```node``` into third party folder to upgrade node.

Not likely the way this plugin is architected (uses embedded nodejs as exe with network pipe).

It does not. Only supports windows at this time.