The StrongLoop CLI allows command line access to StrongOps and other StrongLoop components like the LoopBack API server and the strong-supervisor module, which helps you manage the stopping and starting of servers.
It’s pretty useful, but when there is a chance to upstream useful features to community projects, we try to make it happen.
The “slc debug” command is a wrapper around the node-inspector debugger that starts node-inspector, starts the application to debug, and opens a Chrome browser window with the debugger running in it. Node-inspector maintainer, Miroslav Bajtos, has now pulled this code out and contributed it to the module. The first pull-request is here for those interested, and it has been published to npmjs.org as node-inspector 0.7.0, check it out!
For people used to calling “slc debug”, don’t worry, it hasn’t gone away. The slc command from strong-cli is becoming more “git like”. Instead of having code in the tool itself, it spawns external tools whenever possible to do its work. In this case, “slc debug” continues to exist, but now works by calling “node-debug”. Yeah!
In the process, the command was improved a bit, it now defaults to breaking on the first line (the old ‘slc debug –suspend’ flag), and a few other changes. Check out the docs for the current command syntax.
Use StrongOps to Monitor Node Apps
Ready to start monitoring event loops, manage Node clusters and chase down memory leaks? We’ve made it easy to get started with StrongOps either locally or on your favorite cloud, with a simple npm install.
- Check out Sam Robert’s blog to learn how to debug clustered Node apps using node-inspector
- Check out Miroslav Bajtos blog to learn about what’s new in the latest release of the node-inspector 0.7 debugging module
- Ready to develop APIs in Node.js and get them connected to your data? We’ve made it easy to get started with LoopBack either locally or on your favorite cloud, with a simple npm install.