Challenge 1: Why WebStorm's Node.js Debugger Uses the "Same Inherited" UI — Solution Walkthrough

Why this framing is accurate:

Per this chapter's own material, the debugging UI itself — breakpoints,
stepping, the Variables pane — is inherited from the shared JetBrains
platform, the same underlying component this course has already
traced through PyCharm (Chapter 6) and back to Android Studio's own
Chapter 4. WebStorm doesn't need to build a completely separate
debugging interface for Node.js; it reuses the identical shared
debugging infrastructure every other JetBrains IDE already has,
simply attaching that same UI to a different kind of running process
— a Node.js process instead of a JVM or Android runtime.

Why this matters:

This is a direct, concrete illustration of Chapter 4's own shared-vs-
language-specific framework: the debugging UI itself falls on the
shared side, while what WebStorm specifically adds — attaching to and
debugging Node.js processes — is the JavaScript-specific piece built
on top of that shared foundation, not a separate debugger reinvented
from scratch for this one language.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that "the same inherited debugging UI" is
understood as a specific, structural claim connecting back to this
course's own recurring shared-platform framework, not just a loosely
similar feature that happens to look alike across IDEs.