https://github.com/node-inspector/node-inspector
前提
1.npm install -g node-pre-gyp
https://github.com/mapbox/node-pre-gyp/wiki/FAQ
On Windows for Node C++ modules that do not link external libraries there are no major gotchas. The binaries you build will work well on any Windows system. This is because the default linking for Node is /MT (aka RuntimeLibrary:0) and node-pre-gyp modules inherit this setting by default. So, the C++ runtime will be statically linked into the addon binary and therefore you don't need to worry about your users installing it separately.
However, for Node C++ modules on Windows that depend on external shared libraries, you'll need to understand whether those libraries were linked with /MD or /MT. If the external DLL was linked with /MD then you'll likely need to also link your Node C++ addon using /MD and you'll need to ensure that your users have the right C++ runtime installed for your addon binary to work. For example, if you compiled your binary with Visual Studio 2013 then your users would need This "C++ Redistributable".
2.npm install -g node-gyp
3.https://github.com/nodejs/node-gyp 官方推荐如下命令
npm install --global --production windows-build-tools --vs2017
https://github.com/felixrieseberg/windows-build-tools
4. npm config set python /path/to/executable/python2.7
npm config set python 'C:\Users\clu\.windows-build-tools\python27'
安装
npm install -g node-inspector
使用
貌似不需要使用这玩意了：
Node Inspector is a debugger interface for Node.js applications that uses the Blink Developer Tools (formerly WebKit Web Inspector).
Since version 6.3, Node.js provides a built-in DevTools-based debugger which mostly deprecates Node Inspector, see e.g. this blog post to get started.
The built-in debugger is developed directly by the V8/Chromium team and provides certain advanced features (e.g. long/async stack traces) that are too difficult to implement in Node Inspector.