Simplify Your Database Migrations Using LoopBack 4

by Miroslav Bajtoš - Dec 12, 2018

As applications evolve and developers add new features, the structure of the backing database evolves as well. In LoopBack 3, we provided JavaScript API for automatic migration of database schemas. Recently, we improved LoopBack 4 to leverage these APIs and provide an easy-to-use database migration tool available from the command-line.

For example, when the developer adds a new property to a model, they also need to define a new column in their SQL database schema. NoSQL databases like Cloudant and MongoDB don’t require schema, but still require developers to define indices to speed up frequent queries.


In the Loop - December 2018

by Dave Whiteley - Dec 6, 2018

“In the Loop” provides a monthly rundown of some interesting news, updates or opinions for Node.js, OpenAPI Spec, Microgateway, LoopBack and other open source solutions. We list them in no particular order, and any opinions expressed in the linked posts do not necessarily reflect those of the StrongLoop or IBM team.


LoopBack 4 November 2018 Milestone Update

by Nora Abdelgadir - Dec 5, 2018

With winter approaching, daylight hours have been decreasing, but the LoopBack team’s productivity has not. After we published the General Availability (GA) release, the team started to focus on user adoption and fixing up documentation to accomodate for the increase in users. You can check out the November Milestone here and our December Milestone here.


The Journey to Extensible Request Body Parsing for LoopBack 4

by Raymond Feng - Dec 4, 2018

LoopBack 4 makes it easy for developers to implement business logic behind REST APIs as controller classes in TypeScript and expose them as HTTP endpoints by decorating such classes and their members including methods and parameters. The framework leverages OpenAPI specification compliant metadata to abstract away how to route incoming HTTP requests to corresponding controller methods and make sure the parameters are extracted, parsed, coerced, and validated for method invocations. You can find more details at routing and parsing.


How We Built a Self-hosted REST API Explorer in LoopBack 4

by Miroslav Bajtoš - Nov 28, 2018

The LoopBack team has always believed it’s important to provide great user experience not only to REST API creators, but also to developers consuming those APIs. API Explorer is one of tools making a big difference, as it can render a live documentation for the REST API provided by any LoopBack application and even provides UI controls for executing individual endpoints straight from the docs.

LoopBack 4.0 GA initially relied on an instance hosted externally at With the recent improvements in our REST layer, we were able to introduce a self-hosted version that works fully offline.