Deploying custom Javascript Worker

Reg Paling reg.paling at
Fri Mar 4 06:48:11 UTC 2022

Hi Paul,

Yes I did copy the node_modules folder and also my custom 
lokanet_modules folder into the runtime tree.

I am trying to avoid having to run npm on the end-user workstations.  I 
am hoping it can all be configured to be self-contained.  (Obviously the 
built-in Omnis part is self-contained.)  I'm shooting for a totally 
self-contained Medicare interface!

ERRATA: Actually the HASHWorker call works, but the call to a 
JAVASCRIPTWorker calling omnis_test does not work.


On 4/3/2022 5:21 pm, Paul Mulroney via omnisdev-en wrote:
> Hi Reg,
> When you deployed your custom module, did you also copy over the node_modules folder inside your custom module folder?
> Have you tried running "npm update" after installing in the destination?
> Regards,
> Paul.
>> On 4 Mar 2022, at 1:41 pm, Reg Paling <reg.paling at> wrote:
>> Hi all,
>> I have written a custom Node module which I now want to deploy with my runtimes.  I use the Deployment Tool to build my runtime app, and the resulting app works on my development computer.
>> But when I copy it to another computer, calls to the built-in Omnis modules (such as HASHWorker and a JAVASCRIPTWorker calling omnis_test) work properly, but calls to a JAVASCRIPTWorker calling my custom module hang.
>> I'm pretty sure I have my omnis_modules set up properly.
>> One difference is that I have Node installed on my dev Computer, whereas on the deployment computers it's not installed.  I don't want to have to install Node - I want my runtimes to use the Node which Omnis has built-in.
>> Any ideas?
>> Thanks,
>> Reg
>> _____________________________________________________________
>> Manage your list subscriptions at
>> Start a new message -> mailto:omnisdev-en at
> Hayfever is much achoo about nothing @gingermeggs

More information about the omnisdev-en mailing list