JavaScript Newsletter: 26th November 2020

JavaScript Newsletter: 26th November 2020

·

4 min read

Todays newsletter has quite a variety of technologies, so hopefully there will be something for everyone. The first article is about ES6, which has been out for a while, but introduced some cool features to JavaScript that you might not yet know about. Next we have a Getting Started guide for Nuxt.js, which is what I personally use for a lot of my projects, and I would highly recommend it. Finally we have an introduction into using GraphQL with Node.js, which is currently a very popular way of creating APIs.

Quote of the Day

“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?” - Brian Kernighan

Todays Articles

ES6 and the road to react

By Rutik Wankhade

The thing with JavaScript is that it takes a week to learn the basics but ages to understand it completely. Even though I have worked with JavaScript a lot, I still get stuck and feel uncomfortable sometimes. So this week I decided to dive deep into it.

Getting Started With Nuxt.js - The How & Why

By Asaolu Elijah

Nuxt.js is an intuitive vue.js framework (yeah, a framework’s framework) for building faster and scalable - static, server-side rendered (SSR) & single page applications (SPA’s). Nuxt.js is lovable because its included with vue core plugins by default (vue-router, vuex, vue-head,...), so no extra effort in installing them.

Getting started with GraphQL and Node.js

By Ramon Morcillo

The main purpose of this server-client Node.js project is to help other people understand how GraphQL exposes the data from the Server and the Client fetches it. I have tried to make it as simple as possible- if you want to dive into the code of the project you can find it here. Now, straight to the point: GraphQL is a query language for APIs developed and open-sourced by Facebook to speed up the request process. While REST has been a popular way to expose data from a server, instead of having multiple endpoints that return fixed data structures, GraphQL just has a single endpoint and it is the client's job to specify what data it needs from it.