In this blog post, I describe how you can ignore node_modules by bidirectionally syncing into a cloud directory (as managed via Dropbox etc.).

In this blog post, we examine several approaches for creating instances of classes: Constructors, factory functions, etc. We do so by solving one concrete problem several times. The focus of this post is on classes, which is why alternatives to classes are ignored.

Working with Node.js streams is much more pleasant if we use asynchronous iteration. This blog post explores how to do that.

In this blog post, we take a closer look at how the ECMAScript specification sees JavaScript objects. In particular, properties are not atomic in the spec, but composed of multiple attributes (think fields in a record). Even the value of a data property is stored in an attribute!

In this blog post, we examine the role of type coercion in JavaScript. We will go relatively deeply into this subject and, e.g., look into how the ECMAScript specification handles coercion.

These are lookaround assertions in regular expressions in JavaScript:

• Positive lookahead: (?=«pattern»)
• Negative lookahead: (?!«pattern»)
• Positive lookbehind: (?<=«pattern»)
• Negative lookbehind: (?<!«pattern»)

This blog post shows examples of using them.

In this blog post, we look at npm packages that contain both ES modules and CommonJS modules.

This blog post answers the following questions:

• What is shared mutable state?
• Why is it problematic?
• How can its problems be avoided?

ts-loader has one downside: We can’t pipe the output of another loader into it; it always reads the original file. As a work-around, we can use babel-loader to compile TypeScript. This blog post explains how.

In a web app of mine, I wanted to let end users run multi-module JavaScript that they enter via text fields. It turns out that this simple idea is relatively difficult to implement. In this blog post, I’ll explain how to do it. It is less polished than usual – I mainly wanted to get the knowledge out there.