Continue Learning

I hope that you had a pleasant and enriching experience reading this book and watching the videos. It sure was for me!

I think I've covered close to 80 percent of the language. In this chapter, I'm going to point out a few additional resources that will bridge that 20 percent gap (at least partially). In addition, as I wrote way back in the intro, I think that it's important to differentiate instruction. Some of the links I reference here (and did in the various "Further Reading" sections) duplicate some of this book's content, albeit in a different voice. That's a good thing :). Here they are:

General Topics

Testing TypeScript

TypeScript in the Wild

There are many open source projects written in TypeScript. Here's a small selection. Take some time to read through their code, get a sense for their project structure and how they use TypeScript features:

TypeScript and Node

Converting Plain JS to TypeScript

Advanced Topics

The Grand Summary

This concludes Yet Another TypeScript Book! Thank you for reading!. If you found it helpful (or not!) I hope you'll send me some feedback or even contribute some new content. I already wrote about that in the introduction, but here it is again while I have your attention :)

I think that most authors, and I count myself among them, derive immeasurable satisfaction from reader feedback. If you'd like to contribute to the book in a non-material, spiritual way (like "attaboy!" or "Dear Lord, what fresh hell have you visited upon the world with this book!"), the easiest thing is to simply send me a note to [email protected]. It would be helpful if you put the words "TypeScript Book" in the subject, but certainly isn't required. I always get a little extra pep in my step when someone leaves a comment on one of my blog posts or reaches out by email. It's better than being paid7.

I have long been impressed, interested and even a bit envious of the You Don't Know JavaScript series. Kyle Simpson obviously hit a nerve and he has a really thriving Github project going. I have, in fact, tried to follow his model. If you'd like to participate in a more material way, hit up this book's github site,

  • Star the project
  • Log some issues
  • Correct problems you find and issue a pull request
  • Suggest and even write entire new areas of content and issue a pull request

I will make every effort possible to respond to your emails, review and manage github issues and honor high quality pull requests.

Thank you and best of luck.

results matching ""

    No results matching ""