April 13, 2020

Serving up webpages via a node app turns out to be a whole thing. As it stands, Node’s built-in HTTP module won’t do the trick to serve multiple pages. A handful of pages would be mo problem; a series of them would become a problem. And this, only because I would have to hard code every single end point, and that is not ideal.

Therefore, I’m getting into Express.js. I’ve avoided working into a framework or library up to this point, as I wanted to learn the ins and outs of JavaScript without any additional tools. But now that I feel I have a good handle on API calls, I feel comfortable turning to something like Express to do some work. So here I am, learning Express.

Comments? Follow me on twitter and drop me a line in response to this tweet:

Day 002: I have a good handle on making API calls using Node’s built-in HTTP module. And hard-coding a myriad of if statements is a bad idea. So I’m looking into Express.js. This link goes nowhere, but will go somewhere soon: https://t.co/H4wBFHDGSI#nonsensemod365 pic.twitter.com/1xjyCWSNry

— Joshua Alexander (@nonsensecodes) April 14, 2020