book

Effective TypeScript

Name: Effective TypeScript
Author: Dan Vanderkam
ISBN: 9781492053743

by Dan Vanderkam

October 2019

Intermediate to advanced

261 pages

6h 14m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Preface
Who This Book Is ForWhy I Wrote This BookHow This Book Is OrganizedConventions in TypeScript Code SamplesTypographical Conventions Used in This BookUsing Code ExamplesO’Reilly Online LearningHow to Contact UsAcknowledgments
1. Getting to Know TypeScript
Item 1: Understand the Relationship Between TypeScript and JavaScriptItem 2: Know Which TypeScript Options You’re UsingItem 3: Understand That Code Generation Is Independent of TypesItem 4: Get Comfortable with Structural TypingItem 5: Limit Use of the any Type
2. TypeScript’s Type System
Item 6: Use Your Editor to Interrogate and Explore the Type SystemItem 7: Think of Types as Sets of ValuesItem 8: Know How to Tell Whether a Symbol Is in the Type Space or Value SpaceItem 9: Prefer Type Declarations to Type AssertionsItem 10: Avoid Object Wrapper Types (String, Number, Boolean, Symbol, BigInt)Item 11: Recognize the Limits of Excess Property CheckingItem 12: Apply Types to Entire Function Expressions When PossibleItem 13: Know the Differences Between type and interfaceItem 14: Use Type Operations and Generics to Avoid Repeating YourselfItem 15: Use Index Signatures for Dynamic DataItem 16: Prefer Arrays, Tuples, and ArrayLike to number Index SignaturesItem 17: Use readonly to Avoid Errors Associated with MutationItem 18: Use Mapped Types to Keep Values in Sync
3. Type Inference
Item 19: Avoid Cluttering Your Code with Inferable TypesItem 20: Use Different Variables for Different TypesItem 21: Understand Type WideningItem 22: Understand Type NarrowingItem 23: Create Objects All at OnceItem 24: Be Consistent in Your Use of AliasesItem 25: Use async Functions Instead of Callbacks for Asynchronous CodeItem 26: Understand How Context Is Used in Type InferenceItem 27: Use Functional Constructs and Libraries to Help Types Flow
4. Type Design
Item 28: Prefer Types That Always Represent Valid StatesItem 29: Be Liberal in What You Accept and Strict in What You ProduceItem 30: Don’t Repeat Type Information in DocumentationItem 31: Push Null Values to the Perimeter of Your TypesItem 32: Prefer Unions of Interfaces to Interfaces of UnionsItem 33: Prefer More Precise Alternatives to String TypesItem 34: Prefer Incomplete Types to Inaccurate TypesItem 35: Generate Types from APIs and Specs, Not DataItem 36: Name Types Using the Language of Your Problem DomainItem 37: Consider “Brands” for Nominal Typing
5. Working with any
Item 38: Use the Narrowest Possible Scope for any TypesItem 39: Prefer More Precise Variants of any to Plain anyItem 40: Hide Unsafe Type Assertions in Well-Typed FunctionsItem 41: Understand Evolving anyItem 42: Use unknown Instead of any for Values with an Unknown TypeItem 43: Prefer Type-Safe Approaches to Monkey PatchingItem 44: Track Your Type Coverage to Prevent Regressions in Type Safety
6. Types Declarations and @types
Item 45: Put TypeScript and @types in devDependenciesItem 46: Understand the Three Versions Involved in Type DeclarationsItem 47: Export All Types That Appear in Public APIsItem 48: Use TSDoc for API CommentsItem 49: Provide a Type for this in CallbacksItem 50: Prefer Conditional Types to Overloaded DeclarationsItem 51: Mirror Types to Sever DependenciesItem 52: Be Aware of the Pitfalls of Testing Types
7. Writing and Running Your Code
Item 53: Prefer ECMAScript Features to TypeScript FeaturesItem 54: Know How to Iterate Over ObjectsItem 55: Understand the DOM hierarchyItem 56: Don’t Rely on Private to Hide InformationItem 57: Use Source Maps to Debug TypeScript
8. Migrating to TypeScript
Item 58: Write Modern JavaScriptItem 59: Use @ts-check and JSDoc to Experiment with TypeScriptItem 60: Use allowJs to Mix TypeScript and JavaScriptItem 61: Convert Module by Module Up Your Dependency GraphItem 62: Don’t Consider Migration Complete Until You Enable noImplicitAny
Index

Content preview from Effective TypeScript

Chapter 7. Writing and Running Your Code

This chapter is a bit of a grab bag: it covers some issues that come up in writing code (not types) as well as issues you may run into when you run your code.

Item 53: Prefer ECMAScript Features to TypeScript Features

The relationship between TypeScript and JavaScript has changed over time. When Microsoft first started work on TypeScript in 2010, the prevailing attitude around JavaScript was that it was a problematic language that needed to be fixed. It was common for frameworks and source-to-source compilers to add missing features like classes, decorators, and a module system to JavaScript. TypeScript was no different. Early versions included home-grown versions of classes, enums, and modules.

Over time TC39, the standards body that governs JavaScript, added many of these same features to the core JavaScript language. And the features they added were not compatible with the versions that existed in TypeScript. This left the TypeScript team in an awkward predicament: adopt the new features from the standard or break existing code?

TypeScript has largely chosen to do the latter and eventually articulated its current governing principle: TC39 defines the runtime while TypeScript innovates solely in the type space.

There are a few remaining features from before this decision. It’s important to recognize and understand these, because they don’t fit the pattern of the rest of the language. In general, I recommend avoiding them to keep the ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781492053736Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Effective TypeScript

by Dan Vanderkam

Chapter 7. Writing and Running Your Code

Item 53: Prefer ECMAScript Features to TypeScript Features

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.