Deploying custom Javascript Worker

[Paul Mulroney]

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 lokanet.com> 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 https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 


Hayfever is much achoo about nothing @gingermeggs
-- 
Paul W. Mulroney                                            We Don't Do Simple Pty Ltd 
pmulroney at logicaldevelopments.com.au       Trading as Logical Developments
www.logicaldevelopments.com.au                   ACN 161 009 374 
Ph: +61 8 9458 3889                                       86 Coolgardie Street
                                                                         BENTLEY  WA  6102