node-inspector

问题 I have an meanjs application running on a vagrant box. My vagrantfile is as follows config.vm.network "forwarded_port", guest: 27017, host: 27016 #mongodb config.vm.network "forwarded_port", guest: 1337, host: 1338 #node inspector config.vm.network "private_network", ip: "192.168.33.10" node inspector configuration is as follows 'node-inspector': { custom: { options: { 'web-port': 1337, 'web-host': 'localhost', 'debug-port': 5858, 'save-live-edit': true, 'no-preload': true, 'stack-trace-limit

问题 I am using npm start to start my MEAN stack application, but I would like to use the node-inspector to debug some Mongoose. I know I can start the node inspector with node-inspector , but what can I substitute node --debug app.js with to make npm start work in my case? This is my MEAN stack directory structure: HTML views/ Angular.js public/javascript/ Express.js routes/ Node.js app.js Mongoose js models/, connected in app.js Mongo db connected in app.js For more information, this is my

问题 I can't seem to debug mocha scripts. I am able to run node with inspector like this node --inspect script.js . This then gives me a url to go to to debug, something like chrome-devtools://devtools/remote/... However, when I use mocha with this line mocha --inspect test.js I am not able to debug. It says 'Debugger listening on [::]:5858'. Is there any way for me to debug a mocha test using node's inspector? Going to localhost:5858 gives me this info: Type: connect V8-Version: 5.1.281.84

问题 I know how to debug http applications using node-inspector and iisnode. But can I use node-inspector to debug a non http node application, on windows? I tried: node debug test.js It says: debugger listening on port 5858 But opening http://localhost:5858/ in Chrome does not do anything. BTW: running node debug test.js does start the command-line debugger which works. But it's nothing like node-inspector. 回答1: To use node-inspector, the right switch is node --debug not node debug Here are the

问题 I use node-inspector a lot . When I edit my code and restart, I get the inevitable Detached from the target Error when a new process starts. I always have to go find the tab node inspector is on and restart it. I was wondering if I could avoid this. For example, send a message to node-inspector from node to tell the browsers tab running node-inspector to restart. 回答1: Cross-posting slightly from this SO, with an update to this topic. There is a link in Chrome (58) standard Developer Pane

问题 I am trying to debug my intern test using node inspector. I followed all the steps correctly from here. I gave it a run by performing the following command Start Selenium[for intern test] Run the intern test in node environment C:\node\node --debug-brk node_modules/intern/runner.js config=tests/intern In another cmd I run the node inspector node-inspector --web-port=9999 & Start the browser http://127.0.0.1:9999/?ws=127.0.0.1:9999&port=5858 I can see all the script of my project. I have break

问题 I've tried to install and run node-inspector with a bunch of different commands and still unable to run it: Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ node-inspector -bash: node-inspector: command not found Here is my configuration Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ node -v v0.10.15 Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ npm -v 1.3.5 I installed using: Jordans-MacBook-Pro:angular-express-blog jordanbaucke$ sudo npm install -g node-inspector

问题 Tried to install v8-profiler on Windows7(64 bit) npm install v8-profiler Note: 1. The dependency was Python 2.7, I have installed and set the env. var. also Confirmed 'Visual C++ Redistributable Package' is installed. node-gyp module is also installed But still the error thrown is as follows: D:\Projects\Projects\MY_Prjct3\MY_Prjct>npm install v8-profiler npm http GET https://registry.npmjs.org/v8-profiler npm http 304 https://registry.npmjs.org/v8-profiler > v8-profiler@3.6.2-1 install D:

问题 I use node-inspector to debug JS with Chrome version 54.0.2840.99. I enter "node-inspector" in one windows cmd console and "node --debug-brk l:\dev\debug\test.js" in another windows cmd console. Open "http://127.0.0.1:8080/?ws=127.0.0.1:8080&port=5858" in Chrome. It's able to debug as usual. But I input "1 + 2" in Chrome console, press "Enter" , nothing happen. I would expect "3" is output to Chrome console. It did work with Chrome version 48.0.2564.116. I did not test with other Chrome

问题 I run node with node --debug app OR node --debug-brk app it responds debugger listening on port 5858 Express server listening on port 1338 I now start node-inspector node-inspector --web-port=5859 It responds with Node Inspector v0.3.2 info - socket.io started Visit http://127.0.0.1:5859/debug?port=5858 to start debugging. Open chrome and go to http://127.0.0.1:5859/debug?port=5858 Console logs the following Using TCPview, it shows node is listening to port 5858 but it has no established