LoopBack Drops Support for Node 0.10 and 0.12

At the end of October 2016, the Node project stopped official support of version 0.10. At the end of 2016, the project will also stop supporting v0.12. The primary trigger was that the OpenSSL project no longer supports the OpenSSL versions included in Node v0.10 and 0.12. As a result, there will be no more security fixes for OpenSSL in these release lines.

How is LoopBack dealing with these changes?

The LoopBack team has long wanted to use ECMAScript 6 (ES6, also known as JavaScript 2015) constructs such as the classes and arrow functions. But doing so would require raising the minimum supported version of Node. We started the discussions many months ago, but the need to support users running on old Node versions outweighed benefits of ES6.
Read more

Webinar: Build Simple Search APIs with LoopBack and ElasticSearch

We have a new webinar coming up on December 20th – how to build simple search APIs with LoopBack and Elasticsearch!


Erin McKean (Lead Developer Evangelist, IBM Cloud) is the webinar speaker and will demonstrate how to use LoopBack to help you build APIs to take advantage of the search capabilities of Elasticsearch. Erin explained what else people could expect from the webinar:

“Although Elasticsearch has a built-in RESTful API, it can be tricky to secure and you may not want to expose details to your users. Using LoopBack, we’ll show how to build a simple limited API connecting to Elasticsearch that still takes advantage of its powerful search capabilities.”

When: December 20, 2016
Virtual door opens at 12:45 pm EST
Webcast starts at 1:00 pm EST

Register Now!

Working with File Storage and LoopBack

Update for March, 2017: One of the things I mention at the very end of this article is how file uploads will overwrite each other if they use the same name. I fixed this with a pull request that was accepted a few days ago. By using a new configuration option, nameConflict:makeUnique, files will automatically be renamed with a UUID and their original extension. I recommend *always* using this option!

I’ve got a confession to make: I absolutely love LoopBack. How much do I love it? Before I even joined the StrongLoop team at IBM I was blogging on LoopBack and giving presentations on it as well. I basically told the person interviewing me that it didn’t really matter if they hired me or not; I was going to evangelize LoopBack because I thought it was the coolest thing since sliced bread and beer. In general, I love LoopBack and every aspect of it. However, it doesn’t mean that it is perfect. Today I’m going to discuss a feature that is—in my opinion—somewhat “rough”. I’m not saying to avoid it, not at all, just be prepared for a somewhat bumpy ride. Ready?

So, one of the things that LoopBack makes incredibly easy is handling data in a persistence system. You define a model, let’s say Cat, various properties and types, and then LoopBack can handle persisting that in a variety of different storage mechanisms, from Oracle to MySQL to MongoDB. It just plain works, which is cool. However, the data we’re typically dealing with are simple strings represented in JSON. What about binary data?
Read more

Tell us about your LoopBack Node.js Project at Node Interactive North America

If you’re a Node.js developer or engineer using LoopBack, we’d love to talk to you at Node Interactive North America!

Node Interactive NA

Our StrongLoop Video team will be chatting with engineers for about 10-15 minutes to discuss their project and why they are using LoopBack to make it happen. We’d love to share your story too, and we’d like to reward you for your time with a cool IBM backpack stuffed with swag!

Interested? Visit this page, provide your contact information below and we will get in touch!