Node.js

[getnamo]

@Helghast

Hi, very good plugin.
but to solve the following error, when loading dependencies (ipc-event-emitter) I had to copy the entire Plugins/Content/Scripts directory to my [ProjectRoot]/Content/Scripts.
Is this correct? I thought I only had to indicate in Plugins/Content/Scripts/package.json the dependency to load.

@getnamo

You’re initial thought is correct, the copying shouldn’t be necessary. Just did a test, but it appears it has memory for the last executable path and the old node instance doesn’t close always. After using the task manager to kill the stray node.js server and re-running the main script (either by restarting project or by running with bStopMainScriptOnNoListeners = true and exiting session) and then re-running again, the main script initializes correctly and will remain functioning as long as you don’t move the folder. At that point it will pull the correct dependency folder instead of a different old path.

Opened two new issues regarding these bugs here:
Hysteresis for old node path · Issue #8 · getnamo/NodeJs-Unreal · GitHub and Quitting with main script running doesn't always stop node instance · Issue #9 · getnamo/NodeJs-Unreal · GitHub

Hopefully this silly workaround can be fixed with something proper.

Made some small changes which should fix the lack of node instance stop on exit (issue 9). Not sure if issue 8 has been fixed though. Made a simple test project release with the updated plugin here: Release Early Test v0.4.2 for UE 4.23 with Example Project · getnamo/NodeJs-Unreal · GitHub Check out the NodeJSExampleProject-v0.4.2.7z release which should be a drag and droppable project with two maps, one for simple.js and another for adder.js. Adder.js should test the auto-resolve dependencies. Let me know if that version works for you.