Why do people prefer TypeScript with most of the JavaScript frameworks?

Absolutely. var behaves differently from let and const, and it’s reasonable to think you may need that behavior. For me, this has become more pertinent with my growing usage of async/await. Take the following code. getData(userID) .then( (userProfile) => { return userProfile.name } ).catch( (err) => { log.error(`Hit a snag: ${err}`); })This is the standard promise flow. But async functions allow a more recognizable synchronous flow. let userName = await getUserName(userID);But wait! There’s not error handling in this! That’s ok, because this is now good, old-fashioned synchronous JavaScript. We can just use a try/catch! try { let userName = await getUserName(userID);} catch(err) { log.error(`Hit a snag: ${err}`);}Only, this won’t work. Both let and const are block-scoped, and a try statement is a block scope. the variable userName won’t be available outside of that try block. Best practices dictate pre-declaration of variables to the block in which they will be used, like so: let userName;try { userName = await getUserName(userID);} catch(err) { log.error(`Hit a snag: ${err}`);}I find that ugly, though, especially if you are getting a whole bunch of async variables. I don’t want to write a stack of variables then define the same stack later on. I find it much easier to take advantage of var’s function scoping and both declare and define variables within the try block. That is only one example that I encounter frequently. Again, because var behaves differently, if you desire that different behavior, use it! Don’t only use let and const because of some bizarre dogma promulgated by people who barely know fizz-buzz. read less