Brian,

MoI's WebKit interface determines what resources are available for the Node Editor uses to ensure stability. My Javascript version is 1.7. ES6 or ES11 would more likely be on a different environment like a backend server Node box. The Node Editor startup scans the scripts and begins the background services. The scripts are scanned and linked in their filename order.

loadScripts('core', 'lang, compatibility, colors, geometry, main, editor');
loadScripts('nodes', 'macros, basic, logic, points, curves, solids, construct, transform, objects, interface');
loadScripts('nodes/extensions/libs', '*');
loadScripts('nodes/extensions', '*');
loadScripts('core', 'init, ext.*');

If you want to build a library calling other Javascript files, they have to be scanned (note filename order) before they are available for the other libraries to use.

Example directory:
1test.js
2test.js
3test.js (uses 1test.js and 2test.js and 4test.js)
4test.js

3test.js can use 1test.js and 2test.js libraries but not 4test.js library because it has not been scanned. Error will trigger on a missing script. It is not missing.

4test.js will have to be renamed to 0test.js in both 3test.js and it's filename.

New listing:
0test.js
1test.js
2test.js
3test.js (uses 1test.js and 2test.js and 0test.js)


Wayne