Closed AshisheKumar closed 9 months ago
I have updated Node to v18.17.0 LTS till then I am facing this issue, please help
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
Hi @AshisheKumar,
Can you please provide a little more information of what command your ran and what errors are you facing. It is difficult to understand your situation if you do not provide any information.
I'll get back to you after you provide necessary code and errors in the issue.
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
Which Operating System you are using . If you are using Windows then You have to chnage to change your security settings in powershell after that nodemon will work
Hey people, when I try to run to nodemon it tells me that the command in not found, and when I try to install it globally it says "A complete log of this run can be found in: ...." it only works when I install it using npm i --save-dev nodemon. I want to use it globally, any help ?
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
Did you check if nodemon was installed to package.json/package-lock.json? Try running npm i nodemon where your Dockerfiles are located at and recreate the Docker images.
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
I think @AshisheKumar has left the building - thanks others for trying to help and get more information. I've seen people have trouble previously but it's always been windows and some funky set up.
Going to close. Hopefully someone can be find the "definitive" solution to this (if you search closed issues, you'll see this again). If we do find the answer, please send me a PR into the FAQ 🙏
nodemon -v
:Expected behaviour
Actual behaviour
Steps to reproduce
If applicable, please append the
--dump
flag on your command and include the output here ensuring to remove any sensitive/personal details or tokens.