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.

LoopBack 4 November 2018 Milestone Update


Local API Explorer

From the Self-hosted API Explorer epic, a local version of API Explorer is now supported. As part of the feature, we added a config option to disable API Explorer redirects. There was a lot of discussion surrounding adding the local version feature. You can see the PR and read a related blog post for more details.

For the same epic, we added a page for Serving Static Files in LoopBack 4.

Extending Request Body Parsing

LoopBack 4 processes HTTP requests including the request’s path, query, and body. However, the body is more complex to parse than the other parts of the request. Now, as LoopBack has started to use Express again, it would be in our interest to use Express’ body-parser. The main entry point to handling body parsing from body-parser is RequestBodyParser, which is an extension point to provide body parsing functionality for LoopBack 4 REST APIs. You can see the PR and docs page. Also, keep an eye out for an upcoming blog post with more details.

Improving Component Bindings

We introduced an improvement for the component design to allow contribution of bindings and classes. Now component classes can be declared as follows:

class MyComponent implements Component {
  bindings = [Binding.bind('x').to.(1)];
  classes = {'binding-key-for-my-class': MyClass};
  constructor() {}

You can see the PR for more information.


Documentation Clean Up

This month, the team focused on cleaning up the documentation for LoopBack 4. We opened a spike to look through the docs to make sure they are still up-to-date with all the changes LoopBack 4 has been through. There are various in the documentation need to be updated to reflect the enhancement and features we have put in. Some of the examples are listed below:

  • We’ve updated the how-to guide in exposing GraphQL due to the enhancement in OASGraph.
  • We added a “How-Tos” section to better categorize our guides. See the PR.
  • With the introduction of lb4 repository and lb4 service commands, we have updated the TodoList and SOAP Web Service Calculator tutorials to make use of these commands.
  • We added how to contribute with Webstorm.
  • We updated our Deploying to IBM Cloud page, including fixing the image links, and added more information on how to create a Clouddant database service on IBM Cloud. See the PR.

Additionally, with the release of LoopBack 4 GA, LoopBack 3 packages were moved into Active LTS mode.

Database Migration

A user request asked for documentation outlining how to do datasource migration in LoopBack 4, similar to how it is shown for LoopBack 3. Now calling app.migrateSchema() after the application is bootstrapped will update the database schema at the start of running your application. A custom script was also developed for updating the database schema explicitly. For more details, see the PR and its follow-up.

Unified Website Experience

We gave our loopback.io Documentation and API Docs websites a new look to match our LoopBack 4 theme, which was present on v4.loopback.io. This is part of our epic to have a unified website experience.

Our team has also been working on an easy no-code alternative to Postman to help you test and monitor your APIs. As part of the website update, you will see a Test Your API button. “Automated, collaborative, and powerful API testing and monitoring” is what you get. Check it out and let us know what you think!

LoopBack 3


A few weeks ago we refactored the generator repository generator-loopback by upgrading its dependency yeoman-generator from version 0.x to the latest 3.x. We also released a new major version(generator-loopback@6.x) for this change. In November, the cli repository loopback-cli is updated accordingly to adopt the new generator-loopback, which means the lb * commands now invoke the upgraded generators.

Mongodb Connector

The connector now supports the string to decimal conversion for nested decimal128 properties. You can read the document to learn this advanced feature. This also inspires us to have decimal as a built-in type in LoopBack 4 since it’s a popular data type that’s been supported in most SQL/NoSQL databases. Check this issue to know more about this proposal and join our discussion.

We also released a new major version loopback-connector-mongodb@4.x to get rid of the deprecation warning caused by the outdated url parser. As mongodb 3.2 became LTS in September 2018, we updated the mongodb server to 3.4 on the CI virtual machines, and start to support 3.4 features like decimal128 properties and case insensitive indexes.

New LoopBack Maintainer Hugo

We would like to welcome Hugo (@yaty) who joined our team of maintainers this month! Hugo has been actively working on LoopBack posting comments, questions, and suggestions. We look forward to working more closely with him and seeing his future contributions.

This month, we have been excited to see a significant increase in the number of LoopBack users – through the number of downloads on npmjs.org and increasing number of incoming GitHub issues. As Miroslav stated earlier in a blog post, we need to grow our number of maintainers in order to sustain the growth of LoopBack 4. With that said, we are constantly looking for more maintainers to help us with the project. So, if you haven’t done so already, you can start today by joining our user group.

Call to Action

LoopBack’s future success depends on you. We appreciate your continuous support and engagement to make LoopBack even better and meaningful for your API creation experience. Please join us and help the project by: