I’ve been thinking about this project since late 2015, but it was not until two years later that I started seriously working on it. The project scratches two itches of mine:
Some technical highlights of the projects are:
A mock server is an incredibly useful tool when developing frontend applications. There are many great open source mock servers, each with its own ideal use case, its pain points, and its compromises. mock-server is another one of them, employing a code-over-configuration approach and trading automation (developers have to write their mock endpoints’ logic) for flexibility (developers can write their mock endpoint’s logic).
How do you structure an Express project? How do you validate input parameters? How do you generate a Swagger definition for the implemented API? Express is a low-level framework, and these questions are purposefully left unanswered, allowing its community to come up with many solutions for many use cases. convexpress is one such solution, establishing a set of lightweight and straightforward conventions for structuring Express projects, and offering developers a series of facilities when they follow them.
A Node.js library which allows to create (and destroy) a filesystem structure given a json definition. It’s intended to be used when testing code that deals with the filesystem, as a replacement for filesystem mocks that are often unable to reproduce all the odd behaviours of real filesystems.
There is no such thing as
.properties files in Node.js land, and services
typically read their configurations straight from
process.env. env makes
the process a bit less verbose, and a bit more safe.