NiM (Node.js --inspector Manager)
Streamlines your development process
- Why I wrote NiM https://june07.com/blog/inspect-broke-my-workflow/
- Custom DevTools feature: https://june07.com/blog/nim-custom-devtools-url/
Easier than about::inspect (chrome://inspect/#devices)
NiM manages the Chrome DevTools window/tab lifecycle leaving you with more ability to focus on what matters... debugging your code. You no longer need to copy/paste DevTools URL's or continue opening/closeing tabs/windows.
NiM automatically detects the URL that is generated when running node (locally or remotely) with --inspect option. NIM provides you with the option of automatically opening and closing Chrome DevTools in a tab or window. Just toggle the Manual/Auto setting and then start a debugging session. DevTools will open either on clicking the "Open DevTools" button or after the specified timeout period. If set to auto close, once you end your debugging session, DevTools will close automatically.
- Manage and monitor local and remote debugging sessions
- Manual or automatic control of DevTools interface
- Open DevTools in a new tab or window
- Make DevTools focused or inactive on start
- Customize duration between v8 Inspector probes
- Autosave settings
Setup / Usage / How To
Simple and basic... just install the Chrome Extension in any of the following ways:
- Install via our site: https://june07.com/blog/nim-inline-install or...
- Install via Chrome Web Store: https://chrome.google.com/webstore/detail/gnhhdgbaldcilmgcpfddgdbkhjohddkj or...
- Download .crx file directly from releases as shown here:
Need Additional Information?
- NiM post install page provides some help https://june07.com/blog/nim-install
- Debugging NiM itself https://june07.com/blog/debugging-nim
Note: At the time of writing, the v8 --inspect option is fairly new. See https://nodejs.org/api/debugger.html#debugger_v8_inspector_integration_for_node_js for additional details on the option.
Any and all feedback is encouraged and welcome. Send us an email!