When attaching to a process with a preset breakpoint, when the script file in which it is set is not loaded yet, it seems to bind it to a different file with the same leaf name that is already loaded. Furthermore, it adjusts the breakpoint location so that it is valid for that different file, but the adjustment is applied also to the original file.
The common scenario where this is hit is remote debugging an Express app generated by the express.cmd tool. It generates a file named routes\index.js, which is not loaded until the corresponding URL is hit. If I attach to the process before it is hit, the breakpoint is instead resolved to node_modules\express\node_modules\connect\node_modules\pause\index.js.
The common scenario where this is hit is remote debugging an Express app generated by the express.cmd tool. It generates a file named routes\index.js, which is not loaded until the corresponding URL is hit. If I attach to the process before it is hit, the breakpoint is instead resolved to node_modules\express\node_modules\connect\node_modules\pause\index.js.