freeCodeCamp Project: Timestamp Microservice

Before we get started you can view the project requirements here. You can also get this code on to follow along here.

This is a pretty simple straight forward project where we will accept a UNIX timestamp or a ‘natural language’ date in our url and if valid will return an object containing both the UNIX timestamp and ‘natural language’ values.

For example http://localhost:8080/December%2015,%202015 will return:

  "unix": 1450166400,
  "natural": "December 15, 2015"

Or http://localhost:8080/1504506722 will return:

  "unix": 1504506722,
  "natural": "September 3, 2017"

One thing to note here is that a UNIX timestamp is location specific, namely GMT, so as I am in California as I write this, http://localhost:8080/0 will actually give me the date ‘December 31, 1969’ rather than what you might expect, ‘January 1, 1970’.

For this project we are going to be using Express.js in our Node.js environment. The first thing we will need to do is get our project folder ready, what I like to do is create a new repository on, give it a name, select ‘Initialize this repository with a README’ and done, hit ‘Create repository’. Once that is finished copy the ‘Clone with HTTPS’ link to your clipboard and open up your terminal. Now navigate to your projects folder or wherever you want the project to live locally and run the following:

git clone

You should now have a folder for your new project with just a few git files inside.

The next thing I like to do is run:

npm init

This will run the npm package wizard where you can name your project, name the author etc. Once you have done this, open up your new package.json file and add:

"private": true,
"dependencies": {
  "express": "4.x"

This will ensure that your project is not accidentally added to the main npm repository and it will also state that you are going to be using Express.js in this project. Save your file and close it before returning to your terminal and running:

npm install

Now that we have got our package set up and our dependencies installed we should commit our package back to, assuming you’ve got git all set up at this point that might be as simple as this:

git add -A
git commit -m "this can be any message you like"
git push origin master

Now the next thing I would do is create my actual server file, server.js, this is where all the magic of this project will happen.

The Code

We start our project off as you might expect, requiring the express module and setting the variable ‘app’ to an instance of it:

var express = require('express');
var app = express();

The only other variable I declare out here is an array of the months, this will be helpful when we create Date objects as the month part of a Date object is zero indexed (0-11). We can then check the indexOf('December') which will be 11, perfect once we are parsing our ‘natural language’ dates and making UNIX timestamps:

var months = ['January', 'February', 'March', 'April', 'May', 'June', 'July', 'August', 'September', 'October', 'November', 'December'];

Now we jump into our actual server responses, starting with a simple response on the home URL that show the user some example API calls:

app.get('/', function(req, res) { 
  res.send('<p>Example usage:</p><code>http://localhost:8080/December%2015,%202015</code><br><code>http://localhost:8080/1450137600</code>');

We are only going to have two other server responses, one if the query is numbers and the other is the query starts with letters. First we will deal with the numbers / UNIX timestamp. Express.js is very helpful in that it allows us to use RegEx to route our queries. Here is my our GET request router for numbers:

app.get('/:date([0-9]*)', function(req, res) {...

The :date part is an Express.js placeholder which will give us access to that property at . The RegEx then says take any number, 0-9, followed by anything. This RegEx could certainly be better but it works for us for this simple example.

Next we create out ‘result’ object which is what will be returned by our API, we initialize it with ‘null’ values so that it is ‘reset’ each time and the correct values if they exist are added before the object is return as a response.

var result = { "unix": null, "natural": null };

Next we pull these numbers out and set them equal to a variable called ‘timestamp’. We have to use parseInt because these param values come as a string:

var timestamp = parseInt(;

Now we create a new Date object using this timestamp:

var date = new Date(timestamp * 1000);

Now can set our ‘unix’ value in our result object to the value of our ‘timestamp’ variable.

result.unix = timestamp;

Then we build our ‘natural’ value in our result object by taking the Month, Day and Year from our newly created Date object. Also notice how we use the Month value as the index to pull our actual Month name from our ‘months’ array:

result.natural = (months[date.getMonth()]) + ' ' + date.getDate() + ', ' + date.getFullYear();

Then finally we send this response back to the browser (this also closes our app.get() code block):


Now we move onto our final server response route which deals with a ‘natural language’ date, I use quotes because its actually pretty rigid about how it will take the date but it looks like its natural language. The date must be in the format: September 3, 2017. Again we use Express.js RegEx routing to pick up GET requests that start with letters:

app.get('/:natString([a-zA-Z]*)', function(req, res) {...

Here we use the placeholder :natString which again we can access as req.params.natString and our RegEx that says anything with a lower or uppercase letter followed by anything. Again this RegEx is pretty rudimentary but for our use it gets the job done. If we were to expand or further develop this API this would be one of the first places to start.

The next thing we do, as before, is create our result object containing null values:

var result = { "unix": null, "natural": null };

After this we take our ‘natural language’ date string and split it up into an array, at this point the input ‘September 15, 2017’ would return ['September', '15,' '2017']. Notice the comma after 15, we will need to deal with this later.

var dateArr = req.params.natString.split(' ');

Now we validate if the first item in our array, which should be a month, can be found in our array of months that we created at the start. If it is not, we treat this API request as invalid and return the result object with the null values:

if (months.indexOf(dateArr[0]) > -1) {...

If it is indeed in our array of months we treat this as a valid request and start parsing out our date values as required, here we come across one of JavaScripts wonderful quirks, days as you might expect take values from 1-31, years again as expected take a value such as 1995 which indeed corresponds to the year 1995 but months do not follow this convention and are 0 indexed, so December is represented by 11, January by 0 and so on. This is where our array of months that we created at the start will help us, we can check the index of the first value that the user provided which now lives in our dateArr variable and this will be perfect for building our new Date object:

var month = months.indexOf(dateArr[0]); 
var day = dateArr[1].replace(',', ''); 
var year = dateArr[2];

The only other thing to note here is that our day value still contains a comma. We trim this off simply using .replace().

Now that we have our date values parsed we build our new Date object:

var date = new Date(year, month, day);

And with this we can pull our UNIX timestamp and date values.

result.unix = date.getTime() / 1000;
result.natural = (months[date.getMonth()]) + ' ' + date.getDate() + ', ' + date.getFullYear();

Really we could have just joined our dateArr back together to give our ‘natural language’ date but by passing it into the Date object and pulling it back from there it feels more fool proof to me, once we do the reverse on a date, UNIX to ‘natural language’ or visa versa this makes sure they are correct rather than just assuming.

The last thing we do in this if () code block is pass the result object back as a response from the server:


Outside this if () code block the next thing we see is the default server response that will return the result object with the null values if our ‘natural language’ date is considered invalid:

  res.send(result); res.send(result);

As you can see this closes our final app.get() code block, the final piece of code is our app.listen() code block which tell the app to listen to port 8080:

app.listen(8080, function() { 
  console.log('App listening on port 8080.');

And that’s it, all done! You can check out this code in full on here.

Please feel free to contact me if you have any questions or have any feedback on my code.

Leave a Reply

Your email address will not be published. Required fields are marked *