Copy link to clipboard
Copied
Hi,
Is this possible to run a JavaScript script (NodeJs) as a background process from a CEP extension?
At the moment, I can run a NodeJs script in the background but only if Node is already installed on the target machine.
I would like to be able to spawn the same Node process used by Adobe instead of using an external Node.
Copy link to clipboard
Copied
I think this is what you are looking for.
How to detach a spawned child process in a Node.js script? - Stack Overflow
Copy link to clipboard
Copied
Hi Trevor,
Thank you. I already know how to spawn a child process from a regular Node executable (as I have been using Node for quite some time). However, I noticed that 'spawning' did not seem to work with the Node used by the Adobe extension (CEP_HTMLsomething) which I believe is a modified Node combined with Chromium (or the other way around).
I will try again, but all my attempts gave me no result so far. Maybe there are some limitations since there is a binding between Node and Chromium?
I tried with the --mixed-context / --separate-context options (thinking I would have access to an unbounded NodeJs with the latter) but still failing.
I eventually did find a not great but working workaround.
Thank you.
Copy link to clipboard
Copied
Hey did you find something about this issue ?
I've been trying to fork, spawn a process also and it is not working.
I've been trying different node workers librairies but didnt work either.
I'm guessing they are not allowing this for performance reason...
Would be interested in knowing what working workaround did you find ?
Thanks
Mat
Find more inspiration, events, and resources on the new Adobe Community
Explore Now