Here’s this week’s recap of the Node.js related blogs we posted last week…
Picking the right editor has always been kind of a big deal for me. I’ve had a pleasure of watching editors evolve and grow over the past few years and have developed a great appreciation for the current state of affairs. I spend hours perfecting my shortcuts, configurations, and plugins—perhaps way too much time actually. In this post I’m going to take a quick look at three editors: Sublime Text, Atom, and Cloud 9 IDE.
Error stack traces in Node have still have some distance to cover to become really useful. The absence of a thread local type context in the asynchronous world of Node, makes error correlation a nightmare. This is complicated by anonymous/non-strict function constructors. Zones and Promises solve the problem to an extent for development time but still face overhead challenges in production time. Logging frameworks like Bunyan, Winston or Strong-Loggerhave provided control over verbosity using logging levels – Debug, Info, Warn, Error and Node specific structure by prepending timestamps, cluster – worker processes IDs, app-names or hostnames and rollover capabilities. The fact remains that these logs have to be humanly monitored almost impossibly and quite a few interesting or abnormal events preluding a fatal condition can be missed. In this blog we discuss a simple but effective solution using StrongLoop Controller and Splunk to tackle many of these challenges.
- Ready to develop APIs in Node.js and get them connected to your data? Check out the Node.js LoopBack framework. We’ve made it easy to get started either locally or on your favorite cloud, with a simple npm install.