Express Gateway Release 1.4.1 over here!

We’re back with brand new fixes, changes, updates and..PROGRESS! Thanks to everyone (you) for making all of this possible. We’re excited to see the project mature. Who’s ready for 1.4.1? Let’s kick it off!

An Update with all the Fixins’

Can you handle it? Well, now the API Gateway correctly handles the HTTP_PROXY environment variable. This fix allows developers to use service endpoints behind a corporate proxy.

Hang tight, we’re still working on having good standards for that code style such as more rules around enforcing consistent code formatting. It’s internal to the codebase so there’s no real impact on users. However; we wanted to share because this project is maturing and transparency is important to us and to our community, like you.

Additionally, we’ve updated ioredis-mock to the latest version(3.4.2 ). So this version adds a layer of polish and shine. We had to workaround a few areas in the previous release in order to complete the client switch. The ioredis-mock update is the last part of adding finishing touches to our support for Redis Sentinel, a feature we released with 1.4. Again, the changes here have little impact on end users, but now it’s fired up and ready to go so definitely worth checking out.

In addition to fixing, we’ve also be reformatting.

They go together, right?

We’ve just updated our ESLint version and made it scan the whole codebase. In case you are not sure what ESLint is all about, it’s a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. You may have already seen JSLint and JSHint, but there are some exceptions with how ESLint works.

  • ESLint uses Espree for JavaScript parsing and an AST to evaluate patterns in code.
  • ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

In addition to all of this, we also took some time to kick the crap out of a small bug that triggered hot reloading mechanism twice on gateway start. However; no files were changed because the root problem was a misconfiguration in chokidar.

More info and breakdown on all of this in the shiny documentation section.


Big Change. Small Release. In an effort to help developers, we lowered the minimal level of severity for a log in order to be printed on the standard output. We lowered it from error to warn. This should (hopefully) help you to reveal issues at a more granular level. When something is going sideways, now you can understand what’s going on in a more clear and concise way.

Moving On

Ooooooo! 1.5.0 is almost here. We’re excited. Check out why!

We would love your support in making it happen and if you’re interested in becoming a maintainer or contributor, now’s the time!

Hit up Gitter and join the rest of the developer community.

Not quite ready? That’s ok!

More Resources