Bird
0
0

You run node --inspect app.js but Chrome DevTools does not connect. What is a likely cause?

medium📝 Debug Q14 of 15
Node.js - Debugging and Profiling
You run node --inspect app.js but Chrome DevTools does not connect. What is a likely cause?
AYou forgot to open <code>chrome://inspect</code> in Chrome
BYou used <code>--inspect-brk</code> instead of <code>--inspect</code>
CYour Node.js version is too new
DYou ran the command without <code>node</code>
Step-by-Step Solution
Solution:

  1. Step 1: Check connection setup

    To debug, you must open Chrome's chrome://inspect page to connect to Node.js.

  2. Step 2: Analyze other options

    Using --inspect-brk is valid and pauses app; Node.js version too new is unlikely cause; running without node would cause error.

  3. Final Answer:

    You forgot to open chrome://inspect in Chrome -> Option A

  4. Quick Check:

    Open chrome://inspect to connect debugger [OK]
Quick Trick: Always open chrome://inspect to connect debugger [OK]
Common Mistakes:
  • Assuming --inspect-brk is required
  • Ignoring the need to open Chrome inspect page
  • Not running with 'node' command

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Node.js Quizzes
Child Processes - Handling child process errors - Quiz 13medium Cluster Module - Cluster vs reverse proxy decision - Quiz 1easy Debugging and Profiling - Debugging with VS Code - Quiz 4medium Error Handling Patterns - Error-first callback convention - Quiz 13medium HTTP Module - Setting response headers - Quiz 14medium HTTP Module - Parsing query strings - Quiz 11easy Timers and Scheduling - Event loop phases and timer execution - Quiz 12easy URL and Query String Handling - Encoding and decoding URLs - Quiz 3easy Worker Threads - Receiving results from workers - Quiz 3easy Worker Threads - Passing data to workers - Quiz 1easy