You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[11:23:26] gulp-node-inspector is using node-inspector v0.12.8
[11:23:26] Visit http://127.0.0.1:8080/?port=5858 to start debugging.
Without the server starting, the debugger is running but no sources are available and when I navigate to the server port (localhost:3000), it is not reachable.
What is required to do to get the exact same behavior as using the node-debug command in the terminal?
The text was updated successfully, but these errors were encountered:
@javaguy No I'm sorry haven't investigate further. I had to focus back on my core project which uses another build tool. I hope you will figure it out!
The issue here is that in addition to running node-inspector, node also needs to be run in debug mode. I was using gulp-live-server, and here is my config to get it to run. The following should have the same behavior as node-debug myserverscript.js:
gulp.task('debug', function() {
// Enable debugging with node-inspector
gulp.src([])
.pipe(nodeInspector({
debugPort: 5858,
saveLiveEdit: true
}));
// Start the server and set the debug flag
server = gls.new(['--debug', 'myserverscript.js'], undefined, false);
server.start();
});
in the terminal the following works:
node-debug build/src/main.js
I therefore assumed the following configuration would lead to the same result:
but I only get the following output:
Without the server starting, the debugger is running but no sources are available and when I navigate to the server port (
localhost:3000
), it is not reachable.What is required to do to get the exact same behavior as using the
node-debug
command in the terminal?The text was updated successfully, but these errors were encountered: