TypeScript Readonly Utility type

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

This is the last of the commonly known interface modifying utility types. Do note there are a few more, but we'll get to those in a later stage as they are a bit more advanced.
I want to go over the Readonly utility type in this article.
Using the read-only type, you can transform a type to be read-only, making it impossible to change after the initial assignment.
Let's retake this user interface.
interface User {
id?: number;
firstname: string;
lastname: string;
age?: number;
}
If we would now assign some information to this object, we could always re-assign it later in our code.
const user: User = {
firstname: 'Chris',
lastname: 'Bongers',
};
user.id = 123;
We can now modify any of the existing properties to be a new value.
And we don't always want that.
So in order to prevent this from happening you can wrap the type used in a Readonly type like so:
const user: Readonly<User> = {
firstname: 'Chris',
lastname: 'Bongers',
};
Which will give us the following TypeScript error.

This Readonly type can be super helpful to represent frozen objects. Or objects that should not mutate on their own.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter