Automated npm package deployments with Typescript and semantic-release

TypeScript, npm, and semantic-release

I’m a big fan of automating boring tasks. While it’s never been easier to create and share great software, handling the mental load of versioning and deployments can get tedious over time. Removing the subjectivity from this process can help to speed up developer velocity and decrease the potential for human error.

In this guide, we will:

• 📦 Create a simple TypeScript npm package with Jest tests
• 🏷️ Explain the concept of semantic versioning
• 💬 Apply commit message linting for consistency
• 🤖 Automate releases with GitHub Actions and semantic-release

📦 Creating our basic Typescript package

As someone with a tremendously uncommon name, I often find myself in the uncomfortable position of having to correct the way that my name is spelt. It would be great to use the liberating power of software to help others figure out if they are spelling my name incorrectly.

Let’s start our journey of creating a new npm package called is-chanon.

> yarn init

We’ll bring in some dependencies.

> yarn add typescript jest