In this blog post, we explore how we can style text that we log to the console in Node.js.

Some of the examples use a Unix shell but most of the code should also work on Windows.

Converting values to strings in JavaScript is more complicated than it might seem:

• Most approaches have values they can’t handle.
• We don’t always see all of the data.

In this blog post we look at:

• The current best practice for deploying library packages: .js, .js.map, .d.ts, .d.ts.map, .ts
• Recent new developments in compiling and deploying TypeScript: type stripping, isolated declarations, JSR, etc.
• What the future of deploying TypeScript might look like: type stripping in browsers, etc.

In this blog post, we examine how we can test types in TypeScript:

• First, we look at the library asserttt and the CLI tool ts-expect-error.
• Then, we consider which functionality could be built into TypeScript.

In JavaScript, code has color: It is either synchronous or asynchronous. In this blog post, we explore:

• The problems caused by that
• How to fix them via synchronous await
• The two downsides that prevent synchronous await from being practical

Today’s announcement by Microsoft:

[...] we’ve begun work on a native port of the TypeScript compiler and tools. The native implementation will drastically improve editor startup, reduce most build times by 10×, and substantially reduce memory usage.

This blog post looks at some of the details behind the news.

In this blog post, we explore what unions and intersections of object types can be used for in TypeScript.

Roughly, TypeScript is JavaScript plus type information. The latter is removed before TypeScript code is executed by JavaScript engines. Therefore, writing and deploying TypeScript is more work. Is that added work worth it? In this blog post, I’m going to argue that yes, it is. Read it if you are skeptical about TypeScript but interested in giving it a chance.

Read this blog post if you are a JavaScript programmer and want to get a rough idea of what using TypeScript is like (think first step before learning more details). You’ll get answers to the following questions:

• How is TypeScript code different from JavaScript code?
• How is TypeScript code run?
• How does TypeScript help during editing in an IDE?
• Etc.

Note: This blog post does not explain why TypeScript is useful. If you want to know more about that, you can read my TypeScript sales pitch.

Now that Node.js has built-in support for TypeScript, we can use it as the foundation of simple playgrounds that let us interactively explore TypeScript code.