title: How to properly set up the V8 Debug Configuration in Eclipse with Nodeclipse for NodeJS
body: <p><strong>Back in the day</strong> I was debugging <code>node.js</code> applications using the <a href="https://code.google.com/p/chromedevtools/" rel="nofollow noreferrer">ChromeDevTools</a>. Breakpoints would be synced or reset on remote, so that no matter what, the breakpoints in the Eclipse breakpoint window would always match the actual breakpoints.</p>
  
  <p>Also, setting up the Source Mapping as <a href="https://code.google.com/p/chromedevtools/wiki/FeatureDebugOnRealFiles" rel="nofollow noreferrer">described here</a> would cause Eclipse to break inside my actual local files, not in a read-only V8 window.</p>
  
  <p><strong>These days</strong>, ChromeDevTools is outdated and unmaintained. I started using Nodeclipse and their V8 debugger.</p>
  
  <p>But now, when debugging, Eclipse keeps breaking on breakpoints I had already unset or removed. Seemingly irregardless of my setting here:</p>
  
  <p><img src="https://i.stack.imgur.com/moUjW.png" alt="enter image description here"></p>
  
  <p>Also, whether or not it's a break point I meant to break on, A new read-only editor opens with the V8 (Chromium) icon in stead of the javascript-icon. If the original name was e.g. <code>index.js</code>, the script that opens is <code>index.js (20).chromium</code>.</p>
  
  <p>What is changed? How exactly does one set up the Nodeclipse V8 debugger for proper breakpoint syncing and source mapping?</p>