In a recent Software Engineering Daily podcast Henry Zhu discussed the Babel project, and shed some light into how the transpiler works under-the-hood.
He touched upon how Plugins can be created to alter the resulting compiled code.
I was very interested in experimenting with this capability.
In this post I wish to highlight the process in which Babel transforms your code, developing several interesting plugins along the way.
Following on from adding Flow to the API project, I now wish to garner further confidence in the code by adding tests.
In this post I will document the process of setting up the test-runner Jest, and adding suitable test coverage to the current authentication example.
We have now settled on how our application will perform user authentication.
I now wish to take a step back and help improve upon our code confidence, by-way of adding the static type checker Flow.
In this article I will document the process of configuring Flow with Babel and Webpack, expanding upon our previous example by adding sufficient typing.
Now that we have setup the Serverless Framework, we can go about investigating how Authentication and Authorisation will be handled within the application.
For this we will be using Amazon Cognito, a fully-managed web service which handles the user sign-up, sign-in and management processes.
Now that we have spent some time working out how the API is going to look, we can move on to building it!
We will start off by configuring the initial API project, setting up a Dockerized Serverless Framework with Webpack and Babel support.