This time, we are going to be creating a request header parser microservice in Node.js. Keep in mind that I’ll be using a set-up similar to that used by the previous two tutorials; for those who have not read them, that means that we’ll be using Express, and code our app using ECMAScript 6 thanks to Babel.
Feel free to go though the creation of a simple Express app post, as well as the set-up for using ECMAScript 6 within your node app.
So you want to learn JavaScript. Know this, the path is dark and full of terrors (take that GoT reference as you’d like), but there are vast amounts of knowledge out there. The internet is the most powerful tool at your disposal, but, with great power comes great responsibility (what’s with the terrible references today anyway?), here’s why:
For every good and reliable source of information in the web, there’s 10 other sources that will do nothing but incur bad practices from the very beginning, and we don’t want that to happen, do we. I won’t teach you anything in this post today, but here’s a list of some of the best books, both free and non-free that you can look at and be confident about.
Know any other great books out there? Great! Post them in the comments section so we can all rejoice in knowledge! Here’s my top three:
Welcome to part two of ECMAScript 6: Why Should I use it? If you missed part one, you can find it here. This time, we’ll be looking at the following features that ECMAScript 6 brings to the developer:
The most commonly used ECMAScript implementation is our good old friend JavaScript. With ECMAScript 6, we get a few invaluable tools that will make our code better, cleaner and faster.
As if that wasn’t enough reason to start learning about ECMAScript 6, over the next few posts, I’ll introduce you to some of the most useful features that you should start looking into right now!
Applications grow in size and complexity by the day, and as new needs arise, new tools do too. Bower is one of them, let me tell you about it.
One day, you’re just bringing in jQuery into your nice little project, and then, suddenly, in a weeks time, you need to keep track of a framework, plugins, JS and CSS libraries and whatnot for this other side thing you’re doing. You may just keep a long txt file with a list of CDNs or an overloaded library folder with all of your favorite resources, and that is okay. You’re just missing out on the greatness of Bower, your new best friend.
Today, I’m going to show you the power of NPM and Bower working in tandem. I’ll expand on this in future posts by bringing in a few more tools (Gulp/Grunt, RequireJS, Webpack/Browserify) that you’ll surely find useful, I promise!
Bower is a very handy tool that fetches and brings in anything that you need for your project. That means libraries, frameworks, assets and, according to the official site, rainbows too. Anything that you may ever need is a few keystrokes away.
Before we get into the matter though, we need to get a couple dependencies set up; namely: NPM (Node Package Manager) and Git. Let’s get started.
StartJS 