nodemon: ctrl+c stops nodemon server and emit errno 130 —— nodemon 1.8.4

"dev": "npm run watch-ts & nodemon dist/app.js"

when I run npm run dev,and then ctrl-c, then node server had ended, but it throw the error that npm ERR! code ELIFECYCLE npm ERR! errno 130

If i directly run npm run watch-ts & nodemon dist/app.js, when i ctrl + c , that is ok.

  • nodemon -v: 1.8.4
  • node -v: v8.4.0
  • Operating system/terminal environment: MacOS High Sierra 10.13.4
  • Command you ran: npm run dev

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 3
  • Comments: 16 (3 by maintainers)

Most upvoted comments

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 ❤️

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 ❤️

You’re all still experiencing it because the only person who sent a PR has failing tests. You’ll need to send a PR to see a change. I’ve got this on my radar, but it’s not a huge deal so I’ve not busted open the code (either) to fix.

No one, besides me, has tried to fix it, so yeah, you’ll still have this “problem”

On Wed, 7 Oct 2020, 04:32 Hagen DeRouen, notifications@github.com wrote:

I’m having this problem with nodemon 2.0.4, node 12.19.0, and npm 6.14.8.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/remy/nodemon/issues/1424#issuecomment-704670645, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAADLBEVMCYOK4NA72RSQ4TSJPOOPANCNFSM4FUX6BIQ .

The issue still persists with nodemon 1.19.0. Why isn’t anyone looking into this? What is error 130 anyways? Where should one start debugging in order to work on a fix?

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 ❤️

please

Also experiencing this on:

OS: macOS Mojave 10.14 Node: 10.10.0 npm: 6.4.1 nodemon: 1.18.4 command: npm run start