Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IronNode – Debug Node.js code with Chrome Developer Tools

github.com

Post reply on HN
Print view View original

11–20 of 25 posts

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#11

Post by jkrems »

snarkyturtle wrote: post #3

How is this any different than: https://github.com/node-inspector/node-inspector

It looks like it works by just reusing the devtools that are part of electron instead of shipping it's own (like node-inspector). That might make it more reliable than node-inspector for basic debugging. But that's only a guess after glancing over the code.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#12

Post by ripter »

richmarr wrote: post #9
josteink wrote: post #7

I thought the Iron* moniker was conventionally reserved for things running on .net (It Runs On Net), like IronPython, IronRuby, IronLisp, IronScheme, etc? Isn't using it for this project going to cause confusion?

I was going to make a snarky remark comparing it to the recent second usage of 'isomorphic' but, to be honest, people will figure it out. I'm putting all this stuff on my list of things not to waste blood pressure on.

I don't think he was trying to be snarky. I thought the same thing when I first clicked on the link.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#13

Post by faceyspacey »

troebr wrote: post #8
faceyspacey wrote: post #5

Earlier quoted context omitted.

Node inspector has a lot of problems. Buggy as shit. And it's time consuming to use the -brk param to make ur app stop on the first line and then attach node inspector, and then switch back to having it not stop on line 1 when testing ongoing calls. That's why it is important what this guy built to automatically attach itself, even if all the other node inspector bugs still exist. It's particularly hard to find ur fi…

Have you tried debugging with webstorm?

I have. I use Meteor, and for Meteor it doesn't support debugging Package code, so that's a no-go for me. But I was impressed by what they were going for in the situations I did get it to work. A few things I miss from the chrome style debugging, but a few new things that were quite useful. In general, debugging for Node needs to be fixed and addressed from the ground-up. It's an afterthought for everyone, which is why we see things happening like chrome dev tools being repurposed. I mean that's not a bad idea, but when the implementation is so clearly a half-assed hack job, it's clear a more foundation-first approach must be done.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#14

Post by jstx »

faceyspacey wrote: post #5
snarkyturtle wrote: post #3

How is this any different than: https://github.com/node-inspector/node-inspector

Node inspector has a lot of problems. Buggy as shit. And it's time consuming to use the -brk param to make ur app stop on the first line and then attach node inspector, and then switch back to having it not stop on line 1 when testing ongoing calls. That's why it is important what this guy built to automatically attach itself, even if all the other node inspector bugs still exist. It's particularly hard to find ur fi…

https://nodejs.org/api/debugger.html

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#15

Post by DiThi »

Incidentally I did something very similar with my private projects and I've been using it for the last weeks. It's basically Electron, with a few lines of code that runs the script you pass in the argument and opens Chrome's dev tools. It's awesome, and much, much better than node-inspector.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#16

Post by jondubois »

Can you set the debug port number or PID of the process you want to debug in case your program runs as a cluster of processes?

I agree that node-inspector is tedious to set up and often doesn't work initially - It does have support for debugging clusters though.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#18

Post by richmarr »

josteink wrote: post #10
richmarr wrote: post #9

Earlier quoted context omitted.

I was going to make a snarky remark comparing it to the recent second usage of 'isomorphic' but, to be honest, people will figure it out. I'm putting all this stuff on my list of things not to waste blood pressure on.

I was honestly trying to be helpful, and was definitely not making a snide remark. Sure, people wondering if this is node running on .Net might click and discover they were wrong, and all is fine. But if his project from name alone is perceived as being related to .NET, he may not reach out to the full audience of web-developers he may be aiming for. And that's a net loss for him. If there's a time to reconsider the…

I didn't think you were being snide, nor did I intent to be. Really don't understand the downvoting behaviour around here.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#19

Post by abritinthebay »

richmarr wrote: post #9
josteink wrote: post #7

I thought the Iron* moniker was conventionally reserved for things running on .net (It Runs On Net), like IronPython, IronRuby, IronLisp, IronScheme, etc? Isn't using it for this project going to cause confusion?

I was going to make a snarky remark comparing it to the recent second usage of 'isomorphic' but, to be honest, people will figure it out. I'm putting all this stuff on my list of things not to waste blood pressure on.

Given that the usage of isomorphic is perfectly correct (it's using the biological, not mathematical, definition) I don't know how you'd do that...
Post reply on HN