kbtz

Just pipe the output of any node process with node-inspector enabled to the inspector function, it will generate a link to connect to the current debugging session...

node --inspect 2>&1 | inspector

You'd better use --inspect-brk instead of --inspect to pause at the first line so you can connect to the inspector first.

To debug my webpack.config.ts I use:

	#!/bin/bash
	# A npm link alternative that avoids duplication of shared dependencies.
	#
	# It will install a packed version of your local package instead of just soft linking
	# the package directory (which would include its own node_modules in dependency resolution).
	#
	# Another advantage is that only files that would be published are included in the packed version,
	# then these extracted files are replaced with links to their original files.
	# Hard links are used since many module resolution and bundling tools might try to resolve
	# soft links to their real paths.

	#!/bin/bash

	if [ ${USER} == "root" ]; then
	echo "Don't run the entire script as root;" >&2
	exit 1
	fi

	# Alternative link for icon file https://drive.google.com/file/d/0B-3KQ_ohu-RFVkJyS1Zfa2NLSVE/view
	ICON="http://img.informer.com/icons_mac/png/128/422/422255.png"

	function ensureVisibility(e, c) {
	let e0 = e.offsetTop
	let eD = e.clientHeight
	let e1 = e0 + eD

	let c0 = c.scrollTop
	let cD = c.clientHeight
	let c1 = c0 + cD

	let visible = e0 > c0 && e1 < c1

	.d3-slider {
	position: relative;
	font-family: Verdana,Arial,sans-serif;
	font-size: 1.1em;
	border: 1px solid #aaaaaa;
	z-index: 2;
	}

	.d3-slider-horizontal {
	height: .8em;