Option to allow stdin to be inherited

[binki]

I have a finicky process which only works if stdin is not a pipe. How can I tell nodemon to not mess with the stdio streams? If I do nodemon -I it still intercepts stdin.

[VictorioBerra]

+1 im using blessed and nothing is clickable. It just vomits out input sequences on my screen.

[stale]

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

[seventyeight]

+1 I'm using blessed and no input possible when running with nodemon.

[remy]

Can anyone create the simplest test case that I can test with? Or even better, dig into the code with a PR to fix?

[dominykas]

I am able to reproduce odd behavior with the readline example code from node docs:

const readline = require('readline');

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout
});

rl.question('What do you think of Node.js? ', (answer) => {
  // TODO: Log the answer in a database
  console.log(`Thank you for your valuable feedback: ${answer}`);

  rl.close();
});

Behavior:

• When running with node, this exits after it receives an answer.
• When running with nodemon it seems to receive the answer, but does not exit. It also accepts rs to restart.
• When running with nodemon -I it seems to not receive the answer
• When running with a nodemon.json: { "restartable": false }: receives the answer and then freezes completely (won't even accept CTRL+C)