Closed ruud00000 closed 1 year ago
Thanks for sharing the issue.
In regards to nodemon not detecting changes, try this:
In the package.json
file, update the debug script line to include the -L
option.
debug": "nodemon --inspect=0.0.0.0:9229 -L server.js"
In regards to Chrome DevTools not showing a Remote Target, click on Configure
next to Discover network targets
, and then add 127.0.0.1:9229
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked
Is this a docs issue?
Type of issue
Information is incorrect
Description
In nodejs->use containers for development section Use Compose to develop locally, when I run
I get output as in nochromedebug.txt
So a bunch of messages after
Debugger listening on ws://0.0.0.0:9229/2b7d2f1a-8c74-401f-a800-e42ededc314d
, unlike the screenshot in the docs.Then
curl --request GET --url http://localhost:8000/notes
seems to work fine. Result:Now shown in the terminal: getnotes.txt
Then when opening Chrome devtools with about:inspect nothing is showing under Remote Target, unlike in the docs and when I then click on 'Open dedicated DevTools for Node' I get a screen with no reference whatsoever to the server.js file, so nothing to debug.
Furthermore when I change something in server.js, unlike in the docs, nothing gets updated, nodemon doesn't restart, nothing logged in the terminal.
Is there something missing in the docs then or is there an issue I could solve?
Chrome version: 114.0.5735.134 (Officiële build) (64-bits) Running on Windows 11 Home 22H2 build 22621.1848 Running terminal in Visual Studio Code that shows this info:
Package.json:
Dockerfile:
Location
https://docs.docker.com/language/nodejs/develop/
Suggestion
Please advise what to do in order to be able to follow the instructions in the docs (and update docs if there is something missing in the docs).