01. Mojito v0.9: Philosophy Behind Changes

We found that our customers liked using mojits to generate content, but were not as keen about the amount of configuration required for the application, routing, and the complications of creating middleware. Some internal teams started gravitating towards a more Express-like way of building their applications as a result because Express did not require so much configuration and the way routing and dispatching requests was more direct and transparent.

Because Mojito had been using Express under the hood to power the server and even parse cookies and request body parameters, it only made sense for the team to rethink how applications are started, use configurations, and implement middleware. The team also become more involved in a project known as Modown, which consists of a set of Node.js middleware. Much of that middleware was designed with Express in mind, making it easier and more natural for the team to apply what was learned to transforming Mojito into more of an Express/mojit hybrid.