Here’s this week’s recap of the Node.js related blogs we posted last week…
Welcome to part three of a three part series that aims to help you get a jumpstart on new and breaking API changes in the upcoming Node v0.12 release. In part one, Alex Gorbatchev pulled out the non-breaking API changes, while in part two he separated out breaking APIs. In part three, Ben Noordhuis details out breaking C++ API changes.
We’ve heard clearly from the Express community that one of the areas that most needs attention is documentation. We have plans to contribute in this area for the short, medium, and long term. In the last few weeks StrongLoop has been collaborating with members of the community and specifically with author and developer Hage Yaapa to improve the Express documentation. Today, we’re releasing a comprehensive guide on migrating from Express 3 to 4. You can find the guide on expressjs.com. Read on for our thoughts on the documentation roadmap.
The latest major version of Express, Express 4, has been out for a few months now. If you haven’t already migrated your Express 3.x app to Express 4.x yet, this post will help you find out the details of what is new in the latest version and how to go about migrating to it confidently. As of writing this, Express 4 is at version 4.8.5, which means the release is at a mature stage for version 4. With all the early issues fixed, now is a good time to migrate Express 4.
If you are a .NET developer and want to start using or just explore Node.js, in this post I will provide you with initial guidance. I will make a practical comparison of .NET and Node.js, focusing on similarities and differences to provide you with a frame of reference for further learning. In Part 2 of this blog post we will introduce Node.js frameworks, tools, and coding practices.
Part 1 of this blog post provided an introduction to Node.js for .NET developers. In this second part I am going to discuss common Node.js frameworks, tools, hosting technologies, and coding practices.
A few weeks ago our friend Matt Debergalis from Meteor reached out and said they’d been seeing intermittent slowdowns on Percolate Studio‘s AtmosphereJS, the package management system for Meteor packages. They could reproduce the problem with enough time and load on certain applications and suspected an issue of libuv or event loop interaction with the fibers infrastructure in Meteor. Read on to learn how we came to a solution.
Welcome to part two of a three part series that aims to help you get a jumpstart on new and breaking API changes in the upcoming Node.js v0.12 release. Inpart one, Alex Gorbatchev pulled out the non-breaking API changes, while in part two he separates out breaking APIs. In part three, Ben Noordhuis will detail breaking C++ API changes.
Ready to start monitoring event loops, manage Node clusters and chase down memory leaks? We’ve made it easy to get started with monitoring either locally or on your favorite cloud, with a simple npm install.
- What’s in the upcoming Node v0.12 release? Big performance optimizations, read Ben Noordhuis’ blog to learn more.
- 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.
- Need training and certification for Node? Learn more about both the private and open options StrongLoop offers.