You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@allObjects
The issue here is that node.js loads dynamically - at runtime - from a structured file system implemented by node.js' require(...) implementation. Espruino does it upfront quasy statically before loading your application main fr0m a fixed directory and there is only one fixed directory (out of the box)... it though follows the node.js module concept.
If you have access to the zwift source and you put all the files in modules folder and remove any path information from the require(), it may work.
You may run into space issues, which you may resolve by minifiying (w/ google closure comiler service. You put the minified files in the modules folder w/ .js.min extension.
Good luck... in a positive way...
How many files are we talking about?
PS: 1st lots of lots of brain/boring coding exercise, then muscle exercise on the bicycle... ;-)