re: dev.to with a TypeScript or Flow frontend codebase? VIEW POST

FULL DISCUSSION
 

All of these arguments are the same ones I made at work last year, and our projects will be in TypeScript moving forward. I can't tell you how many times I've looked at a library for the first time and used the supplied type definitions to really find my way around. Of course, for us the deciding factor was my demo of TypeScript vs PropTypes. I recently saw someone mention on twitter that props have intellisense with PropTypes, but that's not something I've experienced. 🤷

 

Glad to hear your moving to TypeScript. Not sure about intellisense with prop types, but even if it did work, that only covers props in React, not the rest of your codebase.

 

My bias comes from starting with Angular, but I've used it for simple projects, too. I feel like I tell this story all the time. Is VanillaTS a thing now?

I started with TypeScript (TS) using a custom front-end library light years ago (late fall 2014). At that time VS Code did not support extensions! Crazy times. After that all my professional TS experience was/is in Node/React. YOLO

code of conduct - report abuse