question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Kill-Process GUI shown when nodemon restarts

See original GitHub issue
  • nodemon -v: v2.0.9
  • node -v: v12.9.1
  • Operating system/terminal environment: Windows 7, x64 / CMD
  • Using Docker? What image: NONE
  • Command you ran: nodemon / nodemon bot.js

Expected behaviour

During file changes and restarting of nodemon, only the terminal should be showing restarting and the kill-process should be triggered, and there should be no-GUI popping up with the name Kill-process.

Actual behaviour

Same as above but the kill-process Terminal pops up during file changes and restart

Steps to reproduce

I am not sure how that came, I started nodemon as usual and this happened


If applicable, please append the --dump flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.

--------------
node: v12.9.1
nodemon: 2.0.9
command: C:\Program Files\nodejs\node.exe C:\Users\DELL\AppData\Roaming\npm\node_modules\nodemon\bin\nodemon.js --dump
cwd: D:\Discord\Discord Bots\MY Discord Bots\Laterex
OS: win32 x64
--------------
{
  run: false,
  system: { cwd: 'D:\\Discord\\Discord Bots\\MY Discord Bots\\Laterex' },
  required: false,
  dirs: [ 'D:\\Discord\\Discord Bots\\MY Discord Bots\\Laterex' ],
  timeout: 1000,
  options: {
    dump: true,
    ignore: [
      '**/.git/**',
      '**/.nyc_output/**',
      '**/.sass-cache/**',
      '**/bower_components/**',
      '**/coverage/**',
      '**/node_modules/**',
      re: /.*.*\/\.git\/.*.*|.*.*\/\.nyc_output\/.*.*|.*.*\/\.sass\-cache\/.*.*|.*.*\/bower_components\/.*.*|.*.*\/coverage\/.*.*|.*.*\/node_modules\/.*.*/
    ],
    watch: [ '*.*', re: /.*\..*/ ],
    monitor: [
      '*.*',
      '!**/.git/**',
      '!**/.nyc_output/**',
      '!**/.sass-cache/**',
      '!**/bower_components/**',
      '!**/coverage/**',
      '!**/node_modules/**'
    ],
    ignoreRoot: [
      '**/.git/**',
      '**/.nyc_output/**',
      '**/.sass-cache/**',
      '**/bower_components/**',
      '**/coverage/**',
      '**/node_modules/**'
    ],
    restartable: 'rs',
    colours: true,
    execMap: { py: 'python', rb: 'ruby', ts: 'ts-node' },
    stdin: true,
    runOnChangeOnly: false,
    verbose: false,
    signal: 'SIGUSR2',
    stdout: true,
    watchOptions: {},
    execOptions: {
      script: 'bot.js',
      exec: 'node',
      args: [],
      scriptPosition: 0,
      nodeArgs: undefined,
      execArgs: [],
      ext: 'js,mjs,json',
      env: {}
    }
  },
  load: [Function],
  reset: [Function: reset],
  lastStarted: 0,
  loaded: [],
  watchInterval: null,
  signal: 'SIGUSR2',
  command: {
    raw: { executable: 'node', args: [ 'bot.js' ] },
    string: 'node bot.js'
  }
}
--------------

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:19 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
remycommented, Jul 6, 2021

What GUI are you seeing? If you can provide a video or at least screenshots it would be useful.

Once you’ve done that, can you also test by installing npm i -g nodemon@debug and repeat the test?

0reactions
DineshRout779commented, Jul 9, 2021

@DineshRout779 you’ll need to actually tell us what version of nodemon you’re using…

Nodemon :- 2.0.10 Windows :- 7 32 bit

Read more comments on GitHub >

github_iconTop Results From Across the Web

kill process on port when starting node.js app? - Stack Overflow
When I save a file in the project the app restarts. The problem is sometime the previous process on that post does not...
Read more >
nodemon app crashed restart - You.com | The search engine you ...
The "App crashed" error mainly occurs because of syntax errors, so if you're struggling even after you restarted everything, make sure to check...
Read more >
UMass Lowell COMP-4620 Notes for Class No. 9 - Jesse Heines
Step 5: Restart the application or make sure you're running nodemon to restart it automagically (p. 125). ensure that the application runs without...
Read more >
nodemon error restart Code Example - Code Grepper
npm install --save-dev nodemon@latest. ... process.kill(process.pid, 'SIGUSR2'); ... Answers related to “nodemon error restart”.
Read more >
The Node.js Handbook - The Valley of Code
Run the application using nodemon followed by application file name. ... It will not appear in the console, but it will appear in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found