How do ECMAScript Private Fields Work in TypeScript?

This content originally appeared on Posts on LINQ to Fail and was authored by Posts on LINQ to Fail

I was reading the release notes for the TypeScript 3.8 beta the other day and there’s a particular feature in there that caught my eye, Private Fields. This is support for the stage 3 proposal which means it’s a candidate for inclusion in a future language version (more info on the stages can be found here). What I found interesting is that although TypeScript has supported a private keyword it doesn’t actually make the field private, it just tells the compiler, meaning that in “plain old JavaScript” you can still access the field, whereas the Private Fields implementation makes it properly truly private, you can’t access it.

This content originally appeared on Posts on LINQ to Fail and was authored by Posts on LINQ to Fail