Our goal with the next version of LoopBack is to use cutting-edge features and tooling from the Node.js ecosystem. Node.js 6.x will be entering maintenance mode this April, and requires us to provide hacks and polyfills to maintain compatibility, which actively works against this goal. As a result, we are dropping Node.js 6.x support for LoopBack 4. We will continue to support Node.js 8.x, and will be adding support for Node.js 10.x shortly after it is released.

With Node.js 6.x out of the picture, we were able to further simplify our project infrastructure:

  • We no longer need a polyfill for util.promisify as we can rely on the built-in implementation.
  • Our build is simpler with a single compilation target i.e. ES2017. This improves the speed and resource usage of CI builds.
  • The coverage data gathered by our tests are more accurate now, as there is only one JavaScript codebase to measure.
  • We were able to increase our platform coverage in Travis CI instead of having two sets of builds for Node.js 6.x and Node.js 8.x.

Our @loopback/build module, which contains a set of scripts to compile/lint/test TypeScript projects, continues to support ES2015 targets, so projects making use of it can still choose to transpile to ES2015 and ES2017 targets. This allows us to maintain backward compatibility for modules using it outside of LoopBack 4.

Call for Action

LoopBack’s success counts 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: