A few issues that I haven't seen reported yet:
1. It would be nice to see what command is executed when you start debugging. For example, I'm trying to make debugger run mocha tests, but it's failing, because I don't know which command is being piped to node.exe I can't figure out how to fix it. Maybe command should be written into output window.
2. Need an ability to override node.exe command completely. Without adding "Node.js startup file". For example, I might want to run grunt task as a debugging option.
3. Debugger only captures current process. If the command you are running launches another process, it's not being captured, so you can't debug anything by running ShellJS script or Jake task.
4. Might be also nice to not close console window right away and wait for user to hit Enter. Sometimes debugger fails to start node process, and the error message isn't capturable, because console closes so fast.
1. It would be nice to see what command is executed when you start debugging. For example, I'm trying to make debugger run mocha tests, but it's failing, because I don't know which command is being piped to node.exe I can't figure out how to fix it. Maybe command should be written into output window.
2. Need an ability to override node.exe command completely. Without adding "Node.js startup file". For example, I might want to run grunt task as a debugging option.
3. Debugger only captures current process. If the command you are running launches another process, it's not being captured, so you can't debug anything by running ShellJS script or Jake task.
4. Might be also nice to not close console window right away and wait for user to hit Enter. Sometimes debugger fails to start node process, and the error message isn't capturable, because console closes so fast.