react-scripts start does not work with lerna run --parallel --stream

[hugomallet]

Since react-scripts 3.4.1
On macos 10.15.3 (not tested elsewhere)

running the command :

yarn lerna run --parallel --stream start

does not start the webpack dev server.

If i remove all lerna arguments it works :

yarn lerna run start

[abrcdf1023]

I have the same issue need rollback to v3.4.0 currently.

[cevr]

From what I can tell, this only happens when the --stream argument is present

[grahamvo]

I'm also seeing this issue. Tried removing --stream and it still isn't working.

[rettgerst]

we've had several issues using lerna exec/run and use the concurrently package in place of lerna exec/run. it requires a bit of setup but overall has more features and fewer bugs.

[grahamvo]

I ended up reverting back to 3.4.0 for the time being until this is fixed.

[hieuxlu]

This change is introduced by commit 7e6d6cd, and can be worked around by commenting out these lines in node_modules/react-scripts/scripts/start.js:168

   
    if (isInteractive || process.env.CI !== 'true') {
      // Gracefully exit when stdin ends
      process.stdin.on('end', function () {
        devServer.close();
        process.exit();
      });
     // Comment out this line
     // process.stdin.resume();
    }

[ddc22]

Facing this same issue. I think lerna maybe triggering an end after running a task in parallel.

[bukharov]

Instead of commenting out the line I set isInteractive to false, but the issue is still there. Setting CI env to true solves it however.

[rolandvar]

I have the same issue need rollback to v3.4.0 currently.

I have the same issue, rollback to v3.4.0 is working fine for me! Thanks

[soyFerrero]

Maybe something like this.

    const shouldLernaExecExit = Boolean(!process.env.LERNA_PACKAGE_NAME)
    const shouldCIExecExit = Boolean(process.env.CI)  
    const shouldInteractiveExecExit = Boolean(isInteractive)

    const shoudExitProcess = [
      shouldLernaExecExit,
      shouldCIExecExit,
      shouldInteractiveExecExit
    ] 

    if (shoudExitProcess.includes(true)) {
      // Gracefully exit when stdin ends
      process.stdin.on('end', function() {
        devServer.close();
        process.exit();
      });
      process.stdin.resume();
    }
  } )
  .catch(err => {
    if (err && err.message) {
      console.log(err.message);
    }
    process.exit(1);
  }); 

[mwood23]

Potentially related: #8691

[nmchaves]

@ianschmitz thanks for reviewing/merging the fix in #8700 🙏 ! I see this issue is associated with CRA's 4.0 milestone right now, but would you potentially consider including the fix in a 3.4.2 "patch" release?

Our team is trying to upgrade TypeScript, so we need to upgrade CRA to 3.4.1. But if we upgrade to 3.4.1, then we face this issue with Lerna.

For now, we're planning to use the workaround suggested in #8685 (comment) while running our application locally. Anyways, thanks for all your work on CRA!