s-a / iron-node Goto Github PK

Debug Node.js code with Chrome Developer Tools.

Home Page: http://s-a.github.io/iron-node/

License: Other

HTML 7.52% JavaScript 83.48% CSS 9.00%

iron-node's Introduction

Debug Node.js code with Chrome Developer Tools on Linux, Windows and OS X.

This software aims to make things easier 😄. With ironNode you have the full power of JavaScript debugging within Chrome Developer Tools.

Installation

npm install iron-node -g;

Usage

The usage is the same as node. Use iron-node instead of node.
Keep in mind to place the keyword debugger; to a place where you want to stop. Run a debug session with the given JavaScript file.

iron-node PATH_TO_NODE_JS_FILE [--customparm1=foo --customparm2=bar];

Demo

More screenshots and demos

Documentation

Support

https://stackoverflow.com/questions/tagged/iron-node

Contributing

License

iron-node's People

Contributors

Stargazers

Watchers

iron-node's Issues

Windows line endings cause trouble on OSX

I changed run.js to use Unix line-feed and it works.

--compile fails to compile bcrypt

ref #38

git clone --depth=1 https://github.com/ncb000gt/node.bcrypt.js.git c:\git\electron-recompile\tmp\b[email protected]
Cloning into 'c:\git\electron-recompile\tmp\[email protected]'...
cd c:\git\electron-recompile\tmp\b[email protected] && set HOME=electron-gyp && node-gyp rebuild --target=0.30.2 --arch=ia32 --dist-url=https://atom.io/download/atom-shell
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | win32 | ia32
gyp http GET https://atom.io/download/atom-shell/v0.30.2/node-v0.30.2.tar.gz
gyp http 200 https://atom.io/download/atom-shell/v0.30.2/node-v0.30.2.tar.gz
gyp http GET https://atom.io/download/atom-shell/v0.30.2/SHASUMS256.txt
gyp http GET https://atom.io/download/atom-shell/v0.30.2/node.lib
gyp http GET https://atom.io/download/atom-shell/v0.30.2/x64/node.lib
gyp http 200 https://atom.io/download/atom-shell/v0.30.2/SHASUMS256.txt
gyp http 200 https://atom.io/download/atom-shell/v0.30.2/x64/node.lib
gyp http 200 https://atom.io/download/atom-shell/v0.30.2/node.lib
gyp info spawn c:\python27\python.exe
gyp info spawn args [ 'C:\\Users\\Stephan\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'msvs',
gyp info spawn args   '-G',
gyp info spawn args   'msvs_version=auto',
gyp info spawn args   '-I',
gyp info spawn args   'c:\\git\\electron-recompile\\tmp\\[email protected]\\build\\config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'C:\\Users\\Stephan\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   'c:\\git\\electron-recompile\\tmp\\[email protected]\\electron-gyp \\.node-gyp\\0.30.2\\common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=c:\\git\\electron-recompile\\tmp\\[email protected]\\electron-gyp \\.node-gyp\\0.30.2',
gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\Stephan\\AppData\\Roaming\\npm\\node_modules\\node-gyp',
gyp info spawn args   '-Dmodule_root_dir=c:\\git\\electron-recompile\\tmp\\[email protected]',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'c:\\git\\electron-recompile\\tmp\\[email protected]\\build',
gyp info spawn args   '-Goutput_dir=.' ]
module.js:338

    throw err;

          ^

Error: Cannot find module 'nan'

    at Function.Module._resolveFilename (module.js:336:15)

    at Function.Module._load (module.js:278:25)

    at Module.require (module.js:365:17)

    at require (module.js:384:17)

    at [eval]:1:1

    at Object.exports.runInThisContext (vm.js:74:17)

    at Object.<anonymous> ([eval]-wrapper:6:22)

    at Module._compile (module.js:460:26)

    at evalScript (node.js:431:25)

    at startup (node.js:90:7)

gyp: Call to 'node -e "require('nan')"' returned exit status 1. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\Stephan\AppData\Roaming\npm\node_modules\node-gyp\lib\configure.js:357:16)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "node" "C:\\Users\\Stephan\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--target=0.30.2" "--arch=ia32" "--dist-url=https://atom.io/download/atom-shell"
gyp ERR! cwd c:\git\electron-recompile\tmp\b[email protected]
gyp ERR! node -v v0.12.6
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
Failed to compile : bcrypt

Not working on Ubuntu 14.04 node 0.12.6

Note sure if I misunderstood the point of the project, but it's not like it's debugging my node server :(

Node code:

var http = require('http')

var server = http.createServer(function (req, res) {
  res.end('Hello')
})

server.listen(8080)

How I run Iron Node:

iron-node httpserver.js

What I get:

The server seems stopped before running (like with --debug-brk) which is OK I guess, but there is no link between my server and the Iron Node UI.

Custom CSS for the document area

Hi!
I am runnning unit tests in Iron Node.
The test reporter (npm:tape-dom) puts OK/FAIL records into the DOM, which is handy.
Unfortunately, the DOM has no CSS to format those records right.
Is possible to add custom CSS somehow?

Thanks!

Meteor Task Force

I use https://github.com/s-a/electron-recompile to compile native modules against current electron version.

So far it fails for the following modules within electron

sqlite3
ws
bcrypt (https://github.com/ncb000gt/node.bcrypt.js.git)

Further we need

an alias to call ironNode instead of node for meteor command. (see: https://github.com/s-a/iron-node/blob/master/docs/METEOR.md#create-an-alias-for-meteor-as-iron-meteor)
fix ERR_EMPTY_RESPONSE
identify and fix main process exception

Current status is described here : https://github.com/s-a/iron-node/blob/master/docs/METEOR.md

ref: #1

How to debug Mocha tests?

I cannot get iron-node to work with mocha. I have seen and read the page on "How to debug other Node.js command line applications like a Grunt task?" but that did not help.

I am able to debug things running in mocha just fine with node-inspector using:

node-debug ./node_modules/mocha/bin/_mocha ./spec/mytest.spec.js

I have tried the same thing with iron-node along with passing in different arguments.

This works, but the tests all run and don't trigger the debugger.

iron-node ./node_modules/mocha/bin/_mocha -- ./spec/mytest.spec.js

I am using the latest version of iron-node and mocha.
Environment: iojs 3.2.0, Ubuntu 15

Debugger crash when script call process.exit()

This problem happens only when I'm running the script using iron-node and not when running the script using node or node debug. To be more precise: normally the script runs my jasmine test suite and exits. In iron-node is crashes before running the tests.

Debug ES6 via Babel preprocessor ?

Is there a way we can preprocess ES6 code with Babel before running it with Iron node ?

cannot get es6 working

Hi there

I've created an .iron-node.js file with the v8 config options like in

https://github.com/s-a/iron-node/blob/master/.iron-node.js

However I still get the error Unexpected token this.on("change", () => this.stylize() )

Any ideas?

Incorrect console.log

(Edit: had nothing to do with babel/register)

This is my mongoose log when running the application with node

Mongoose: users.ensureIndex({ email: 1 }) { unique: true, background: true, safe: undefined }  
Mongoose: applicationattributes.ensureIndex({ key: 1 }) { unique: true, background: true, safe: undefined }  
Mongoose: couriers.ensureIndex({ key: 1 }) { unique: true, background: true, safe: undefined }  
Mongoose: forms.ensureIndex({ key: 1 }) { unique: true, background: true, safe: undefined }  
Mongoose: inquiries.ensureIndex({ reference: 1 }) { unique: true, background: true, safe: undefined }

This is the one with iron-node.

�[0;36mMongoose:�[0m users.ensureIndex({ email: �[33m1�[39m }) { unique: �[33mtrue�[39m, background: �[33mtrue�[39m, safe: �[90mundefined�[39m }  NativeCollection.(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:123Collection.doQueue @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/collection.js:106Collection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/collection.js:69callback @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:86Db.collection @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/db.js:316NativeCollection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:45open @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:482Connection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:494(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:453(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/conne…:59(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/db.js:200Server.connect.connectHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/server.js:272g @ events.js:260emitOne @ events.js:77emit @ events.js:169(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:373(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:770Callbacks.emit @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:84messageHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:218dataHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:259emitOne @ events.js:77emit @ events.js:169readableAddChunk @ _stream_readable.js:146Readable.push @ _stream_readable.js:110onread @ net.js:520
/Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:123 �[0;36mMongoose:�[0m applicationattributes.ensureIndex({ key: �[33m1�[39m }) { unique: �[33mtrue�[39m, background: �[33mtrue�[39m, safe: �[90mundefined�[39m }  NativeCollection.(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:123Collection.doQueue @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/collection.js:106Collection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/collection.js:69callback @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:86Db.collection @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/db.js:316NativeCollection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:45open @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:482Connection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:494(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:453(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/conne…:59(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/db.js:200Server.connect.connectHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/server.js:272g @ events.js:260emitOne @ events.js:77emit @ events.js:169(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:373(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:770Callbacks.emit @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:84messageHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:218dataHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:259emitOne @ events.js:77emit @ events.js:169readableAddChunk @ _stream_readable.js:146Readable.push @ _stream_readable.js:110onread @ net.js:520
/Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:123 �[0;36mMongoose:�[0m couriers.ensureIndex({ key: �[33m1�[39m }) { unique: �[33mtrue�[39m, background: �[33mtrue�[39m, safe: �[90mundefined�[39m }  NativeCollection.(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:123Collection.doQueue @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/collection.js:106Collection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/collection.js:69callback @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:86Db.collection @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/db.js:316NativeCollection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:45open @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:482Connection.onOpen @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:494(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/connection.js:453(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/conne…:59(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/db.js:200Server.connect.connectHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/lib/server.js:272g @ events.js:260emitOne @ events.js:77emit @ events.js:169(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:373(anonymous function) @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:770Callbacks.emit @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:84messageHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:218dataHandler @ /Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/node_modules/mongodb/node_modules/mon…:259emitOne @ events.js:77emit @ events.js:169readableAddChunk @ _stream_readable.js:146Readable.push @ _stream_readable.js:110onread @ net.js:520
/Users/jonas/Development/3nit/3nit-core/node_modules/mongoose/lib/drivers/node-mongodb-native/colle…:123 �[0;36mMongoose:�[0m forms.ensureIndex({ key: �[33m1�[39m }) { unique: �[33mtrue�[39m, background: �[33mtrue�[39m, safe: �[90mundefined�[39m }

The logs are also rendered like errors. It seems that node-iron doesn't parse the logs as strings, but as the pointers to the functions.
Screenshot: http://i.imgur.com/AOqBHFx.png

process.argv value is invalid

I created 2 little files:

a.js:

require('./b');
console.log('a:', process.argv);

b.js:

console.log('b:', process.argv);

This is what happens when I run it in node (with or without the debugger):

This is what I see when I run it in iron-node:

I expect to see the same values as in Node.

Note that this can be a nasty bug to some libraries that rely on process.argv[1] being the full path to the main file. For example, ratify loops infinitely when it sees process.argv[1] without slashes.

add application setting in .iron-node.js for autoAddWorkSpace

Could it pause on first start?

Sometimes I want to just boot my code without adding a debugger statement.

Is this possible - would be good like

iron-node -b myscript.js

Themes does not work

For example https://github.com/s-a/iron-node-zerodarkmatrix-theme.

"Module version mismatch" error

This is in the console, and it's not starting the server because of it. Hopefully there's enough info in the screenshot for versions - but please let me know if you need more.

It should throw exception on start script errors

Reload program on file change

Is it possible to achieve functionality similar to nodemon? I could, of course, use nodemon but it closes and reopens iron-node.

Cannot debug Gulp Tasks

v8Flags works with a command line command to determine some things. Which fails in Electron Environments. https://github.com/tkellen/js-v8flags/blob/master/index.js#L59

ref: #21

Breakpoints works only in one version of a file

Hello! Firstly, I'd like to say thank you, because I like your project a lot.

But I've faced a problem:
There are 2 version of file accessible by ctrl+p. One is in left tree view (with path like: proj/js/file.js) and another (with full path and no domain: D:\proj\js\file.js). And I cannot realize how to set a breakpoint in the first case. Basically I can set it, but it doesn't work. In second case (full path versions) it works fine though.

I've read readme a few times, and I still cannot solve it :(
P.s.
Is it possible to hide debugger sources from the tree?

Osx screenshot needed

@artem-russkikh can you submit me a cool screenshot from osx as showcast for the website at https://github.com/s-a/iron-node? 😃

Module did not self register

Using node v0.10.33

Developer tools zooming settings are not saved

Subj.

Is it Electron bug?

Add docs to master the breakpoints

ref: #46 (comment)

Move --native to configuration file

process.stdout.write does not output to DevTools console?

The app i was testing with uses bunyan which logs to the console. However when running with iron-node the console/stdout is suppressed for some reason.

Application doesn't start

This is all I'm seeing when I attempt to start our application:

$ iron-node src/app.js --conf="configuration/local.js" --dev
[9504:0929/094939:INFO:CONSOLE(0)] configuration null
[15696:0929/094939:INFO:renderer_main.cc(200)] Renderer process started
[9408:0929/094939:INFO:renderer_main.cc(200)] Renderer process started
[9504:0929/094939:INFO:CONSOLE(141)] "os", source: file:///C:/Users/OliverSalzburg.HARTWIG/AppData/Roaming/npm/node_modules/iron-node/app/app.js (141)
[9504:0929/094939:INFO:CONSOLE(142)] "versions", source: file:///C:/Users/OliverSalzburg.HARTWIG/AppData/Roaming/npm/node_modules/iron-node/app/app.js (142)
[9504:0929/094939:INFO:CONSOLE(143)] "appData", source: file:///C:/Users/OliverSalzburg.HARTWIG/AppData/Roaming/npm/node_modules/iron-node/app/app.js (143)
[9504:0929/094939:INFO:CONSOLE(147)] "configuration", source: file:///C:/Users/OliverSalzburg.HARTWIG/AppData/Roaming/npm/node_modules/iron-node/app/app.js (147)
[9504:0929/094939:INFO:CONSOLE(61)] "scanning", source: C:\Users\OliverSalzburg.HARTWIG\AppData\Roaming\npm\node_modules\iron-node\node_modules\package.js\lib\index.js (61)
[

Running iron-node $(which **) commands fails

Hey I'm on osx. I haven't dug in here super deep. But... whenever I try to debug global modules that run tasks I get a stack of errors. I have tried karma and gulp. I don't know if I'm just doing it wrong. Or if there is something to be fixed.

iron-node $(which gulp) task-name
iron-node $(which karma) start

I do love how much quicker this is than node-inspector.

How can we get this to work with Meteor?

(delete this, if possible)

this totally ended up in the wrong place, sorry.

No log output via visionmedia/debug

Edit:

simple example
npm i --save debug

test.js

process.env.DEBUG = 'dev'
var debug = require('debug')

console.log('test')
debug('dev')('test')

run it with node test and compare it to iron-node test

You will see there is no output in the second case.

Live reload or support nodemon

I ran this:

iron-node $(whence -f nodemon) index.js

and debugger has not been caught

File list duplication

Every time I refresh (Ctrl-r), the files in the file list get duplicated.
New copy of debuggee is probably created in memory, because breakpoints don't work and a new - identical tab with source is opened.

Console output:

D:\projects\sach>iron-node index.js
[4364:0818/011107:INFO:renderer_main.cc(200)] Renderer process started
[3736:0818/011108:INFO:renderer_main.cc(200)] Renderer process started
[1908:0818/011108:INFO:CONSOLE(141)] "os", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (141)
[1908:0818/011108:INFO:CONSOLE(142)] "versions", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (142)
[1908:0818/011108:INFO:CONSOLE(143)] "appData", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (143)
[1908:0818/011108:INFO:CONSOLE(147)] "configuration", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (147)
[1908:0818/011108:INFO:CONSOLE(61)] "scanning", source: d:\bezinst\node\node_modules\iron-node\node_modules\package.js\lib\index.js (61)
[1908:0818/011109:INFO:CONSOLE(99)] "Error in", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (99)
[1908:0818/011109:INFO:CONSOLE(5)] "", source: D:\projects\sach\index.js (5)
[3484:0818/011115:INFO:renderer_main.cc(200)] Renderer process started
[1908:0818/011115:INFO:CONSOLE(141)] "os", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (141)
[1908:0818/011115:INFO:CONSOLE(142)] "versions", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (142)
[1908:0818/011115:INFO:CONSOLE(143)] "appData", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (143)
[1908:0818/011115:INFO:CONSOLE(147)] "configuration", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (147)
[1908:0818/011115:INFO:CONSOLE(61)] "scanning", source: d:\bezinst\node\node_modules\iron-node\node_modules\package.js\lib\index.js (61)
[1908:0818/011116:ERROR:CONSOLE(178)] "undefined", source: chrome-devtools://devtools/inspector.js (178)
[1908:0818/011116:INFO:CONSOLE(99)] "Error in", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (99)
[1908:0818/011116:INFO:CONSOLE(5)] "", source: D:\projects\sach\index.js (5)
[2400:0818/011119:INFO:renderer_main.cc(200)] Renderer process started
[1908:0818/011119:INFO:CONSOLE(141)] "os", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (141)
[1908:0818/011119:INFO:CONSOLE(142)] "versions", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (142)
[1908:0818/011119:INFO:CONSOLE(143)] "appData", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (143)
[1908:0818/011119:INFO:CONSOLE(147)] "configuration", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (147)
[1908:0818/011119:INFO:CONSOLE(61)] "scanning", source: d:\bezinst\node\node_modules\iron-node\node_modules\package.js\lib\index.js (61)
[1908:0818/011119:ERROR:CONSOLE(178)] "undefined", source: chrome-devtools://devtools/inspector.js (178)
[1908:0818/011119:INFO:CONSOLE(99)] "Error in", source: file:///D:/bezinst/node/node_modules/iron-node/app/app.js (99)
[1908:0818/011119:INFO:CONSOLE(5)] "", source: D:\projects\sach\index.js (5)

D:\projects\sach>node -e "console.log(process.versions)"
{ http_parser: '2.3',
  node: '0.12.4',
  v8: '3.28.71.19',
  uv: '1.5.0',
  zlib: '1.2.8',
  modules: '14',
  openssl: '1.0.1m' }

In readme, explain why this is better than node-inspector

What features does this offer over node-inspector?

fails on freeBSD

npm install iron-node -g
|
[email protected] postinstall /usr/local/lib/node_modules/iron-node/node_modules/electron-prebuilt
node install.js

/usr/local/lib/node_modules/iron-node/node_modules/electron-prebuilt/install.js:24
if (!paths[platform]) throw new Error('Unknown platform: ' + platform)
^
Error: Unknown platform: freebsd
at Object. (/usr/local/lib/node_modules/iron-node/node_modules/electron-prebuilt/install.js:24:29)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3
npm ERR! FreeBSD 10.1-RELEASE-p10
npm ERR! argv "node" "/usr/local/bin/npm" "install" "iron-node" "-g"
npm ERR! node v0.12.6
npm ERR! npm v2.1.18
npm ERR! code ELIFECYCLE

npm ERR! [email protected] postinstall: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script 'node install.js'.
npm ERR! This is most likely a problem with the electron-prebuilt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls electron-prebuilt
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /root/npm-debug.log

Duplicate with node-inspector?

What's the difference? advantage? OR purpose?

node-inspector

value of require.main

I just realized, that require.main.filename points to <iron-node install dir>/iron-node/app/index.html
I think it would be beneficial, if require.main contained the module loaded by iron-node, instead of iron-node itself.

I don't currently have any use case for this, so please take this just as a suggestion.
I'm pretty sure there are npm modules that rely on the suggested behavior, though.
Somewhat similar to #36.

Edit: the same applies to process.mainModule

--compile fails to compile ws

ref: #38

binding.gyp not found

Cannot debug Grunt tasks

Reloading?

I know I can hit Command-R to reload the code...but what about integrating some type of mechanism to auto reload code on file change? Or maybe integrate with something already built, like nodemon?

Thoughts?

Add execute software update to main menu

Maybe a weekly running method to check for updates.

(require.main === module) is false for the main module loaded

This is annoying when debugging scripts that can be used as both a command-line utility and a Node module.

Cannot use harmony switches on the command line

I'm running iron-node --harmony_arrow_functions index.js and it tries to load the parameter as a file.

dialog buttons unreachable when error stack trace is very long

Hey @s-a, another awesome project!

When I first launched, I get this error from my project (it doesn't like iron-node very much). The stack trace is so long I couldn't see the buttons on the bottom and there is no scroll bar to navigate down.

Hitting enter navigates me past this error.

Give love to left frame

I understand the importance of the left frame for your own good, but it would be even greater if it would be useful for the debugged project ;) I think the share buttons are pretty useless and could be replaced with a single link to project's homepage, whereas the donation button could be more exposed.

I also imagine very good usages for this frame (all while keeping the donation button and link to homepage). If user could inject any HTML he wants the tool could be used for very nice and various unintended situations:

Training exercices: left frame gives the context, the goal, and user has to edit the code directly in debugger to make it work
General instructions: tell your co-workers about project specifics that may impact the debugging session, maybe tips about dev environment…
This could even be used to add some debugging and profiling pro-tips if nothing is specified by user

gyp: Undefined variable module_name in binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\Stephan\AppData\Roaming\npm\node_modules\node-gyp\lib\configure.js:357:16)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "node" "C:\\Users\\Stephan\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--target=0.30.3" "--arch=ia32" "--dist-url=https://atom.io/download/atom-shell"
gyp ERR! cwd c:\git\electron-recompile\tmp\s[email protected]
gyp ERR! node -v v0.12.6
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok