Nodemon not completing restart of server on change of server side code

[hphvac]

• nodemon -v:
• node -v:
• Operating system/terminal environment:
  node js
• Using Docker? What image:
• Command you ran:
  npm run dev-starts fine-update to code does not

Expected behaviour

Restart of server on server side code change

Actual behaviour

freezes and just repeats restarting due to changes-doesnt actually restart

Steps to reproduce

any change to code-
have updated all dependencies

---

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

[remy]

Hi there, to be able to debug this issue, you're really going to need to provide more information about what you're doing, what OS you're running - and really all the questions you ignored - otherwise this issue will self close because no one will be able to help you :(

[hphvac]

node v-10.15.3
nodemon v-1.19.4
Win 10 running win 32 bit
no docker
Node js is server lang
command i use to start server is npm run dev
reproduces whenever it is supposed to restart

[hphvac]

missed those sorry

[hphvac]

just saw-Visual Studio Code-Version 1.40 October 2019 release

[remy]

Possible the PR #1579 will fix - please re-test when it's live.

[hphvac]

im not sure what that means

[joseph-galindo]

@hphvac #1579 was shipped in nodemon@2.0.0 - try that version to see if your issue has been fixed

[hphvac]

@joseph-galindo -i am sorry, but it did not.

[remy]

@hphvac you're going to need to provide more feedback. Can you start with a screenshot of the output that you're seeing?

[Remzi1993]

Hi @joseph-galindo

You could update your NPM packages by using the @latest tag, see example here under:

npm install -g nodemon@latest

Or

npm install --save-dev nodemon@latest

https://bytearcher.com/articles/using-npm-update-and-npm-outdated-to-update-dependencies/
https://flaviocopes.com/update-npm-dependencies/

[hphvac]

here you go, thank you for your time

[hphvac]

@remy @joseph-galindo Thank you

[remy]

@hphvac can you re-run with the -V flag so we can see what's causing the restart (in the screenshot)?

[hphvac]

@remy I really appreciate the help, but i do not know what you mean by that. What restarts it is the normal action of editing server side code, as it should. but it seems as though it never restarts.
a normal restart looks like this

, however whenever i change code, it just hangs here.

[hphvac]

if you have a reference to refer me to i could learn, but all i know about v flag is version...lol

[Remzi1993]

@hphvac I think he wants you to run it like this:
npm run dev -V

Could you try this?

[hphvac]

@Remzi1993 I did try that, there is no change

[Remzi1993]

Did you also try:
npm run -V dev
Or
npm -V run dev
Also it's capital, npm -v is displaying npm version and this is capital -V
npm <command> --key value and sometimes short variant -tag

EDIT: Oops, he meant run it like this: nodemon -V
If you do nodemon -h you will get a list what you could do with nodemon.

[remy]

@hphvac just to clarify, can you run the nodemon -V command directly instead of npm run dev (on a unix based system I can tell you how to pass arguments through to nodemon, but I'm not familiar with Windows command line capabilities).

Then, just as you have before, screenshot the output that shows nodemon restarting (the -V flag will tell nodemon to print the files triggering the restart).

[remy]

@Remzi1993 the syntax to send arguments from the command line to the script npm is npm run dev -- -V - the double dash is what tells the command line to stop slurping arguments. But I'm not sure it works on Windows.

[hphvac]

When I type in nodemon-v , says it is an unrecognized file I stepped out of the office but I will send it to you when I get back

…

On Fri, Nov 22, 2019, 2:22 PM Remy Sharp ***@***.***> wrote: @hphvac <https://github.com/hphvac> just to clarify, can you run the nodemon -V command directly instead of npm run dev (on a unix based system I can tell you how to pass arguments through to nodemon, but I'm not familiar with Windows command line capabilities). Then, just as you have before, screenshot the output that shows nodemon restarting (the -V flag will tell nodemon to print the files triggering the restart). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1630?email_source=notifications&email_token=AIXQPNKEK6AJIUL3IZNCMELQVAWQLA5CNFSM4JPFX57KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE6TSRA#issuecomment-557660484>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIXQPNNS5ZOBPMDLBQCMQC3QVAWQLANCNFSM4JPFX57A> .

-- *Best regards,* *High **Performance** Heating & Air Conditioning* 2350 Brighton-Henrietta Town Line Road | Rochester, NY  14623 (585) 342-7653  *office | *(585) 426-3007 *fax*   www.highperformanceheating.com <http://www.highperformanceheating.com/>

[remy]

@hphvac you need a space between nodemon and the - and it needs to be a capital V (not lower - a lowercase v will print the version).

[hphvac]

@remy Nice!-Here you go,Thanks!

I also tried adding a delay, no avail.

[hphvac]

@remy @ just got this!

[hphvac]

@remy @Remzi1993 Good morning-i have found that on node error, the app also restarts correctly- seems only to happen on restart as a result of code change- I have also found that it seems as though the server is actually running. Even though it says it is restarting. Basically on a client side request, the server responds-however it is still running the previous processes-in other words-it is still running the unchanged code-

[Remzi1993]

@remy This looks looks like a serious issue. Is this related to #1632 or #1635 ?
Seems like something broke it.

PS: It could also be a naming issue, because everything should be subprocesses right?
In the log I see something about a child.__nodemonRestart?

[remy]

Yes, that's right, but I don't know how child is null/undefined at this point. Possibly makes sense to protect against assigning the prop, but until I can get my hands on Windows to test properly I can't say. I'll try to scrape some time this week with a VM to replicate and debug.

[JonatanOrtiz]

Same problem. I tried all the tips and they didn't solve the problem.

[Habeebullahi01]

I'm running the latest version of nodemon and I still have this problem.

[Silventino]

If you're running on windows, make sure system32 folder is in the path variables.

[Remzi1993]

@remy Seems like folks still have issues with this. Could you kindly re-open this issue?

[remy]

Best to file a new case with code on how to replicate.

[isaacgr]

Found this post which suggested using nodemon app.js -L to set the legacy flag and enable polling. This worked for me on Windows 10. Not sure why its broken though.

[sunny775]

If you're running on windows, make sure system32 folder is in the path variables.

@Silventino you're a f**king genius! This worked for me. Thanks so much

[leleoveiga]

If you're running on windows, make sure system32 folder is in the path variables.

@Silventino geniussssssssssssss, it worked for me too. Thanks so much!

[nilesh-yadav-au6]

@Silventino thanks boss....... worked for me to

[Marwan1998]

@Silventino That Worked for me either, i really want to kiss you 😂, Thanks Alooooooot ❤️

[woojerry]

If you're running on windows, make sure system32 folder is in the path variables.

WOW ~! I tried this problem for 3days and I finally solved it by this. Thank you very much !!!!!!!!!!!!!!!!!!!!!!!!!

[MehedilslamRipon]

If you're running on windows, make sure system32 folder is in the path variables.

what is the path variable? I can't understand. please help...

[Silventino]

If you're running on windows, make sure system32 folder is in the path variables.

what is the path variable? I can't understand. please help...

https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/
follow this tutorial and add "C:\Windows\System32" to the PATH

[Ryzen-thor]

If you're running on windows, make sure system32 folder is in the path variables.

Thanks It worked

[bhavyajain6]

If you're running on windows, make sure system32 folder is in the path variables.

amazing man it workeeedddd. All the big solutions failed it was just this little thing. Thanks a ton man

[ranger-code]

Just Downgrade nodemon version to 2.0.2

[peter571]

Neither of the above is solving my issue

[hphvac]

95% of the problems that I have seen is because node man cannot end the processes that you have going. Find out why it cannot shut down the processes, such as a "for" Loop that gets stuck open.

…

On Tue, Jul 20, 2021, 7:08 PM Peter Koech ***@***.***> wrote: Neither of the above is solving my issue [image: image] <https://user-images.githubusercontent.com/58890899/126406376-bc891c44-43d4-4dee-87ad-f669019776ef.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1630 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIXQPNNPJ64K5XCCFCVZXF3TYX6VRANCNFSM4JPFX57A> .

[ranger-code]

Just Downgrade nodemon version to 2.0.2

it worked for me

[HADMARINE]

Just Downgrade nodemon version to 2.0.2

It worked for me (2)
Downgraded from 2.0.12 to 2.0.2

[RaresTarniceru]

Yep. Downgrade to v 2.0.2, was the only thing for me too. Just write the command npm i nodemon@2.0.2

[GusGF]

Even downgrading to v2.0.2 doesn't work. Yep an error isn't generated but I believe now that nodemon isn't working for me. But since so many are having problems with the latest version why has this thread remained closed?

[mdodge-ecgrow]

Having same issue, Nodemon does not appear to be actually restarting Node after a change. I've verified System32 is in my path. I am on version 2.0.2.

[ghost]

Just Downgrade nodemon version to 2.0.2

Worked for me. Tks man

[HADMARINE]

Even downgrading to v2.0.2 doesn't work. Yep an error isn't generated but I believe now that nodemon isn't working for me. But since so many are having problems with the latest version why has this thread remained closed?

I agree with this thread, it should be open

[remy]

Latest version != this original issue. Track the new issues on the current open issues - they also include some actual information.