node.js - Chrome's node inspector tool blocking TCP access with the CLI? -


if run node application via normal way (just running node --inspect foo.js), able connect running application using chrome dev tools fine.

if, on other hand, node --inspect, , in resultant repl require('foo.js'); server start doesn't have access appropriate tcp ports. in particular in former case can curl http://localhost:3000/ , stuff, in latter econnrefused.

this annoyance, since can write script , run instead of getting inspector started in repl, i'd know is: known setting should toggle somewhere? it's annoying if want fiddle initialization parameters - easier type them in rebuild project each time run script right.


Comments

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

python Tkinter Capturing keyboard events save as one single string -

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -