Chromiun dependency does not work in whatsapp-web.js | electronjs.org | Page 1

fair wagon Sep 20, 2023, 4:52 PM

#

I need help; I'm working on an app using whatsapp-web.js because I'm automating messages. My issue is that everything works fine when I'm in development mode, but when I'm in production, meaning when I'm running the .exe, it no longer works because the whatsapp-web.js library relies on a Chromium instance, which is never executed in production.

// whatsapp-web.js client config
const client = new Client({
  authStrategy: new LocalAuth(),
});

In the image my application in both environments the first task is my application is build in .exe and the second task is my application but in development mode the only difference is that in development my application if it starts chromiun that my whatsapp-web.js configuration need

#

Chromiun dependency does not work in whatsapp-web.js

real mango Sep 20, 2023, 4:53 PM

#

from where chromium instance comes from?

fair wagon Sep 20, 2023, 4:55 PM

#

real mango from where chromium instance comes from?

whatsapp-web.js use it internally because it also occupies pupeeteer how scrapping library

real mango Sep 20, 2023, 4:55 PM

#

puppeeteer doesn work with electron in production

fair wagon Sep 20, 2023, 4:55 PM

#

real mango puppeeteer doesn work with electron in production

why?

real mango Sep 20, 2023, 4:56 PM

#

becase electron unable to run executables

#

in production

fair wagon Sep 20, 2023, 4:57 PM

#

there has to be some kind of solotion

real mango Sep 20, 2023, 5:00 PM

#

you can try to disable asar

fair wagon Sep 20, 2023, 5:01 PM

#

asar? what is it?

#Chromiun dependency does not work in whatsapp-web.js