Is there a way to attach a debugger to ld-r process (VScode debugger, ChromeDevTools, ...) ?
I'm finding difficulties on managing to work a debugger with this isomorphic app bundled with webpack.
I'm not sure (just guessing) but I wonder if the transformation operated by webpack + babel cuts
the map with original files.
Do someone already face this problem?
Expected Behavior
Code execution stops on breakpoint both on client and server files.
Actual Behavior
Breakpoint not working
Steps to Reproduce the Problem
Launch $ node --inspect webpack/dev-server.js from ld-r root directory
attach a debugger to the running process
Navigate to a file and set a breakpoint (in Chrome Dev Tools)
Is there a way to attach a debugger to ld-r process (VScode debugger, ChromeDevTools, ...) ? I'm finding difficulties on managing to work a debugger with this isomorphic app bundled with webpack. I'm not sure (just guessing) but I wonder if the transformation operated by webpack + babel cuts the map with original files. Do someone already face this problem?
Expected Behavior
Code execution stops on breakpoint both on client and server files.
Actual Behavior
Breakpoint not working
Steps to Reproduce the Problem
$ node --inspect webpack/dev-server.js
from ld-r root directorySpecifications