Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugging node by specifiying path of JS file

See original GitHub issue

I seem to be stuck with a really bizarre issue here. I have the node-inspector server running locally. https://github.com/node-inspector/node-inspector#advanced-use I am now trying to run a Node project by specifying the path node --debug-brk /home/naveen/node-atom/index.js the index.js is just a simple one line Node app that prints a console line output. Now when I navigate to chrome at this link http://127.0.0.1:8080/?port=5858 I do not get any attached process. However i get the command line log "Debugger listening on port 5858 ".

On the other hand, If I navigate all the way to the destination package and use the same command node --debug-brk index.js the index.js file is attached as expected.

Am i missing something here? TIA

Issue Analytics

State:
Created 8 years ago
Comments:7

Top GitHub Comments

7reactions

naveenjafercommented, Mar 2, 2016

This is the error that I receive.

Node Inspector v0.12.7 Visit http://127.0.0.1:8080/?port=5858 to start debugging. Debugging/home/naveen/nodeatom/index.js

Debugger listening on port 5858 Access to /home/naveen/node_modules/.bin from ResourceTree denied. (Error: ENOENT: no such file or directory, stat ‘/home/naveen/node_modules/.bin/electron’) Access to /home/naveen/clitrial/node_modules/.bin from ResourceTree denied. (Error: ENOENT: no such file or directory, stat ‘/home/naveen/clitrial/node_modules/.bin/electron’) Access to /home/naveen/atom/node_modules/styleguide/node_modules/.bin from ResourceTree denied. (Error: ENOENT: no such file or directory, stat ‘/home/naveen/atom/node_modules/styleguide/node_modules/.bin/highlights’) Access to /home/naveen/atom/node_modules/markdown-preview/node_modules/.bin from ResourceTree denied. (Error: ENOENT: no such file or directory, stat ‘/home/naveen/atom/node_modules/markdown-preview/node_modules/.bin/highlights’) Access to /home/naveen/atom/node_modules/fstream/node_modules/.bin from ResourceTree denied. (Error: ENOENT: no such file or directory, stat ‘/home/naveen/atom/node_modules/fstream/node_modules/.bin/rimraf’) Access to /home/naveen/atom/node_modules/fs-plus/node_modules/.bin from ResourceTree denied. (Error: ENOENT: no such file or directory, stat ‘/home/naveen/atom/node_modules/fs-plus/node_modules/.bin/rimraf’)`

0reactions

JohnGalt1717commented, Mar 30, 2017

Me too. Same problem.

Top Results From Across the Web

Debug Node.js Apps using Visual Studio Code

Debugging configurations are stored in a launch.json file located in your workspace's .vscode folder. An introduction into the creation and use of debugging...

Running and debugging Node.js | WebStorm Documentation

From the main menu, select Run | Edit Configurations. · Specify the Node. · In the JavaScript File field, specify the path to...

How to Debug Node.js Code Using Multiple Tools - Kinsta

This tutorial demonstrates various tools to debug node applications and find their root causes. Dig in and learn from the ground up.

Debug single javascript file in “Visual Studio Code”

With the file you want to debug open, go to the debugger panel, click the green arrow and choose Node as your environment....

Debugger | Node.js v19.3.0 Documentation

To use it, start Node.js with the inspect argument followed by the path to the script to debug. $ node inspect myscript.js <...