Google Developer Expert | Auth0 Ambassador | Media Developer Expert at Cloudinary | Twilio Champ | Technical Coach at SpringBoard | Google Women Techmaker | Postman Supernova | AWS | Microsoft MVP
I love how you decided to get your questions answer here instead of stackoverflow. I spend a lot of time on SO answering angular questions, but honestly fuck the community there. People are so cocky. Question, what are you doing in the website when it stops? is it always in the same route?
already tried that, but AFAIK I can't post there yet until I already earned some higher level. I don't know if that's still the case, as I only read answers when I ran into some problems, LOL. but going back, I can't find answers in SO, so I posted here. The website did not stop, just the live reload no longer works. I have to ctrl+c then run the npm start again to recompile and see the changes.
Google Developer Expert | Auth0 Ambassador | Media Developer Expert at Cloudinary | Twilio Champ | Technical Coach at SpringBoard | Google Women Techmaker | Postman Supernova | AWS | Microsoft MVP
aahhhhh i seee i seee vscode stops watching your files for change? Am I correct? I encounter that same issue a long time ago like 2 years ago. I think I changed the port and re started my server. Try that maybe.
I love how you decided to get your questions answer here instead of stackoverflow. I spend a lot of time on SO answering angular questions, but honestly fuck the community there. People are so cocky. Question, what are you doing in the website when it stops? is it always in the same route?
already tried that, but AFAIK I can't post there yet until I already earned some higher level. I don't know if that's still the case, as I only read answers when I ran into some problems, LOL. but going back, I can't find answers in SO, so I posted here. The website did not stop, just the live reload no longer works. I have to ctrl+c then run the npm start again to recompile and see the changes.
aahhhhh i seee i seee vscode stops watching your files for change? Am I correct? I encounter that same issue a long time ago like 2 years ago. I think I changed the port and re started my server. Try that maybe.
unfortunately, that didn't work as well.