Process 'command 'node'' finished with non-zero exit value 1

Question

I tried to build jitsi meet based on react-native but it stucks in bundleReleaseJsAnd assets and then throw this error :

Process 'command 'node'' finished with non-zero exit value 1

Do you have any solution for this? – Kartik Shah Sep 05 '19 at 06:47 — Kartik Shah, Sep 05 '19 at 06:47

score 3 · Answer 1 · answered Mar 10 '21 at 12:49

3

In my case I had error in React Native side, I fixed it and I was able to generate bundle

answered Mar 10 '21 at 12:49

Harshil Jasoliya

106
8

plz provide the solution – Muhammad Haris Jun 06 '23 at 12:47

score 2 · Answer 2 · answered Apr 10 '19 at 22:49

2

I solved the problem in my Putting

project.ext.react = [
     entryFile: "index.js"
]

In App build.gradle

answered Apr 10 '19 at 22:49

Antonio Junior

91
4

And what about hermes? – C-lio Garcia Sep 14 '21 at 10:08

Tim Keating · Answer 3 · 2020-07-30T21:41:46.037

Okay so to clarify Sumakh's answer -- this happened to me because I had a build error in my app's JavaScript code. Ergo the build step invoking node to build the runtime bundle threw an exception. To find the script error, there are a couple of options:

I ran eslint against my JS sources, which identified the error, then fixed it, and was off to the races.
After the fact, though, I realized that IntellJ (where I was editing the JS code) had been warning me about the syntax error (showing the red squiggly underline on the file in question)
If you have a pre-existing working runtime, you could also try running the current state of the JS code in your simulator, and it should throw an exception showing you where the bad code is.

score 1 · Answer 4 · answered Mar 04 '19 at 02:45

1

Just kill node process and repeat the build process.

answered Mar 04 '19 at 02:45

Bruno Araujo

435
4
15

how do you do that ? – Hamed Mar 06 '23 at 12:05
first identify process number after `kill -9 ` – Bruno Araujo May 31 '23 at 01:37
and run `ps -ax | grep node` to check node process-number – Tony Wu Jul 07 '23 at 10:27

score -3 · Answer 5 · answered Sep 06 '18 at 15:34

-3

This is because of code style for jshint errors in your HTML files. Use IDE which supports HTML files, and shows errors in HTML if any. Sometimes, errors in the HTML will still work in browser, but build will fail.

answered Sep 06 '18 at 15:34

Sumukh Bhandarkar

386
1
5
14

Process 'command 'node'' finished with non-zero exit value 1

5 Answers5

Linked