📚 Learning and exploring the TypeScript programming language.
TypeScript is JavaScript with syntax for types.
This repository is my own exploration of TypeScript and the TypeScript ecosystem. It codifies some of the TypeScript concepts and trivia I've learned into runnable example programs, complete with verbose commentary and references.
NOTE: This project was developed on macOS. It is for my own personal use.
This repository illustrates different concepts, patterns and examples via standalone subprojects. Each subproject is completely independent of the others and do not depend on the root project. This standalone subproject constraint forces the subprojects to be complete and maximizes the reader's chances of successfully running, understanding, and re-using the code.
The subprojects include:
A "hello world" TypeScript program compiled directly with the TypeScript compiler: tsc.
See the README in hello-world/.
A TypeScript program that showcases enums.
See the README in enums/.
A TypeScript program that showcases union types.
See the README in union-types/.
Exploring TypeScript's utility types which enable powerful type designs using type transformations.
See the README in utility-types/.
General clean-ups, TODOs and things I wish to implement for this project:
- DONE Add an enum example. There are a lot of TypeScript features I want to learn but enums are top of my mind.
- DONE Add a dev container definition. I want to be able to run this in GitHub Codespaces or VS Code Remote Containers.
- DONE Add a "union types" (or similar) example.
- DONE Clean up my
tsconfig.jsonfiles. I can't remember what is important and what is right for 2023.
- GitHub repo:
javascript-playground- This is another project of my own. It contains some TypeScript examples which would be better suited for this project. I'll migrate them over here in the future.
- TypeScript docs: What is a tsconfig.json
- Interestingly, there are TSConfig base files. I didn't know about that before. For example, @tsconfig/node16.
It's intriguing, but it's community-driven and not driven by the TypeScript and there aren't explanations for the
configurations. I'm not sure if I want to create a dependency relationship on this. I might prefer copy and paste.
Update: I'm confused, the TSConfig base I used uses the value "es2022" for "lib" and that isn't even listed
as a value in the official TSConfig docs. It goes up to "es2021" which maybe that needs updating, but still, I'll
stick with official guidance for configuration that I don't have a reason to change. Usefully, Intellij is highlighting
the value with a warning. Update again: ah the official TypeScript docs for
libeven admits "This list may be out of date"! Ok that's fair TypeScript team. Point to you TSConfig base community.
- Interestingly, there are TSConfig base files. I didn't know about that before. For example, @tsconfig/node16.
It's intriguing, but it's community-driven and not driven by the TypeScript and there aren't explanations for the
configurations. I'm not sure if I want to create a dependency relationship on this. I might prefer copy and paste.
Update: I'm confused, the TSConfig base I used uses the value "es2022" for "lib" and that isn't even listed
as a value in the official TSConfig docs. It goes up to "es2021" which maybe that needs updating, but still, I'll
stick with official guidance for configuration that I don't have a reason to change. Usefully, Intellij is highlighting
the value with a warning. Update again: ah the official TypeScript docs for