GitXplorerGitXplorer
g

node-inspector-windows

public
10 stars
6 forks
2 issues

Commits

List of commits on branch master.
Unverified
f25238f10aa138474157ce7d54c65656f307cb5d

Merge pull request #1 from turanuk/master

gglennblock committed 13 years ago
Unverified
2c2913cd446db4ad7d5f2a821c562e020ba99121

Adding support for applying environment variables to node debugging environment

tturanuk committed 13 years ago
Unverified
2886466ee09e5129b244fa93e9209e92d389237e

Update README.md

gglennblock committed 13 years ago
Unverified
d3f19ad257b988b1b704a345a66b35222f09a899

Fixed formatting

gglennblock committed 13 years ago
Unverified
4f03a0a5c57415a913fa900ac1a4dc389e177cba

Initial commit

gglennblock committed 13 years ago

README

The README file for this repository.

Using node-inspector on windows

What is this?

Tool for getting node-inspector working on windows and for simplifying the proces of launching the debugger. It's not rocket science, but it is (I think) useful.

What it does

  • Gets you up and running with a windows friendly version of node-inspector
  • Provides a command line tool to launch for debugging.

Prerequisites for using

Installation

  • From the command window launch install.cmd. This will install node-inspector via npm and apply the paperboy patch described [here] (https://github.com/dannycoates/node-inspector/issues/62#issuecomment-1998429) to get node-inspector working on windows.
  • From the start menu right click on Computer->Properties->Advanced Computer Settings->Environment variables.
    • Create 2 system variables
      • set NODE_INSPECTOR to the folder where this repo is located i.e. "c:\node-inspector"
      • set NODE_INSPECTOR_BROWSER to the path of your webkit browser of choice i.e. Chrome, Safari. For example right clicking on Chrome on my machine gives me “C:\Users\gblock\AppData\Local\Google\Chrome\Application\chrome.exe”
  • Add %NODE_INSPECTOR% to your path.

Using

  • In the command window, go to the folder where the node app you want to debug is.
  • Type node-debug [url] e.g. node-debug http://localhost:3000

Once you run it from the app folder it will:

  • Launch node inspector
  • Launch you app in debug mode.
  • Open the browser you specified and launch the debugger ui.
  • Launch the start url you specified.

Known issues I've seen some cases where running node-debug causes a socket error. This seems to happen periodically. Closing the command windows and starting again seems to clear it.

Acknowledgements

License

  • node-inspector-windows is licensed under Apache 2.
  • paperboy is licensed under the "Debuggable Limited license" (see LICENSE.PAPERBOY.txt)