Node.js and TypeScript

When I first discovered Next.js, I was excited about it, but it has become somewhat of a mess since then. These are my thoughts on it.

As always, there is a lot going on in the world of tech. This week’s “Linker” features experimental updates, new releases and a few tips and tricks.

This is the first of a regular series of posts featuring links of interest to developers and nerds.

For years, my go-to frontend framework was React, but now I prefer using Angular for my projects. This is why.

Vue.js makes it easy to implement router-level code splitting. Page loaders are a great way to indicate that your application is loading.

An operating system that was released 25 years ago and required an entire computer to run can now instead be run in a browser window with an interpreted language.

Visual Studio Code is a tool with many talents. Among those is the ability to not just debug Node.js applications, but also to debug them remotely.

For about two years I have been using Grunt to compile my SASS files into CSS for projects for work as well as for personal projects such as this website. This workflow has served me well and I still use it for most of my PHP-based projects. However, I’ve come up with an even easier and faster solution for my Node.js-based applications.

Since I am constantly starting a new project, I got tired of always having to set up each web app from scratch. Therefore, I decided to create a couple of boilerplate apps in Node.js and TypeScript.

Node.js + Docker + WebStorm is not an unusual setup for Node.js developers, but there is nonetheless surprisingly little information available about how to setup debugging in WebStorm while running a Node.js application locally in a Docker image.