fereturk.blogg.se - Node js windows set debug

NODE JS WINDOWS SET DEBUG UPDATE
NODE JS WINDOWS SET DEBUG CODE

In the above figure, next command will set the debugger on the next line. The above command starts the debugger and stops at the first line as shown below.Īs you can see in the above figure, > symbol indicates the current debugging statement. Now, to debug the above application, run the following command. So, write debugger inside callback function as above. For example, we want to check the "data" parameter in the above example.

NODE JS WINDOWS SET DEBUG CODE

nw.Write debugger in your JavaScript code where you want debugger to stop.

You can also use the remote debugging flag, so you can just pop open a chrome tab and visit the page.

Every time you make a change to your script, go through steps 4-6.Click the hamburger icon and wait for th the inspector window (just like Chrome/Webkit) to start, and go the Console tab.Then wait for node-webkit window to appear.

NODE JS WINDOWS SET DEBUG UPDATE

Update your package.json main attribute to point at the HTML file.Add the script to debug in a tag to the HTML file.node-webkit also has some oddities and changes to the normal Node API which can conflict with your existing libraries or dependencies. This is by far the least efficient method to inspect and view console output because of the long list of steps below. Run path/to/chrome/chrome.exe -app= to open the special node-codein console.Include codein in your script: var codein = require("node-codein").

Instead it uses its own proprietary/special console which feels a bit chintzy. You basically go to chrome://inspect on a stable version of Chrome and it debugs your running Node instance.Ī cross platform NodeJS REPL application based on electron and react frameworks.Įven though this tool uses the Chrome executable, it does not use the Chrome/Webkit inspector console for output. What we aim for Node is what we have for Chrome for Android. The goal is to provide a "unified debugger support across various v8 embedders". This is still in development but you can watch the progress on nodejs/node#2546 Update: devtool is looking to be my new choice.ĭebug Node.js code with Chrome Developer Tools on Linux, Windows and OS X. I prefer NodeMonkey because it uses the awesome Chrome developer console. One nice thing about NodeMonkey( and node-codein suggested below), is that you can leave up the developer console(no refreshes) everytime you make a change and restart the script, NodeMonkey just continues to listen.Īnother thing NodeMonkey has is locations(path, line number, and column), so you know where the message came from (see image below).

Then run your script as normal: node myscript.js.

Open up and inspect element, etc to open up the developer console.

Include NodeMonkey in your script: var nomo = require('node-monkey').start().

This uses Chrome's( webkit) actual built-in Developer Tools Javascript console for output. It captures anything that would normally be logged to the terminal, and passes it to the browser where it is then logged to the console for inspection. Use the devtool command in place of node: devtool myscript.js This allows you to profile, debug and develop typical Node.js programs with some of the features of Chrome DevTools. Runs Node.js programs inside Chrome DevTools (using Electron).

Chrome Logger is the closest so far but you need a response object to piggyback which makes this very unusable if you aren't using node as a web server.

Node Inspector is really just for inspecting variables and adding breakpoints.

Node Inspector which I thought was perfect but turns out their console is just a REPL client that doesn't print the console.log STDOUT calls in scripts.

UltraREPL's readme says that collapsible objects are "In Progress".

Supports oup and other console methods.

Supports copy(ctrl+c), paste(ctrl+v) key shortcuts.

Works as a normal console (like Windows cmd).

Collapsible(expand/collapse) objects (and arrays.).

Like a webkit console window remotely connected to a cmd console session. I am currently using Console2 but I want some expand/collapse handles when console.log'ing javascript objects Just like any modern web browser console has (Webkit, Chrome for example).Ī remote solution is acceptable. I am looking for nice console alternative to use with Node.js.