You can get a lot of the benefits of Typescript in VSCode without leaving JavaScript behind by using JSDoc.<p>Typescript will pick up the JSDoc type annotations and use them to type the code. This can be a great option when typing an existing project.<p>Docs: <a href="https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html#supported-jsdoc" rel="nofollow">https://www.typescriptlang.org/docs/handbook/type-checking-j...</a>
I’ve found this React + TypeScript cheat sheet extremely helpful while recently porting a React codebase to TypeScript. (To the point it’s one of only four bookmarks on my browsers bookmark bar.)<p>Perhaps others here will find it useful as well.<p><a href="https://github.com/typescript-cheatsheets/react-typescript-cheatsheet#reacttypescript-cheatsheets" rel="nofollow">https://github.com/typescript-cheatsheets/react-typescript-c...</a>
It seems that I fundamentally misunderstand the benefits of TypeScript.
I found myself spending hours and hours on reading the type errors stacktraces and adding types for libraries. Writing TS code takes 2x time than simple JS... and it is extremely painful experience.
In comparison to many old plain JS projects I did - it simply doesn’t make any sense, the TS solves problems which I haven’t experienced at all.
Hey all, I work on the TypeScript team. I've been super happy to read some of the posts about the migration on Execute Program. If anyone has any feedback or questions on TS, I can also try to answer them.
I'm not saying I never ever run into bugs due to dynamic types such as method/variable typos, I just think it's much more rare than people make it out to be. If that sort of thing happens a lot in a project you basically have very little tests.
I'm confident in saying it happens to me maybe once in a few months - and that's working in a super dynamic environment of Rails.
The Null error does happen, but that happens in java as well.
I love TypeScript, but have encountered a situation where I simply could not compile my code anymore because it started causing an internal error in the compiler itself.<p>Fortunately, I work as a team lead, and this was on an experimental branch, so I was able to hand off bits of code relating to architectural patterns I was evaluating to my team to continue work on those.<p>But I simply could not proceed with my code as is, a very frustrating experience to say the least. How is this even possible?
Regarding the previous backend related article and code sharing between backend and frontend, how does your project setup look like?<p>For example, does the code get compiled using a bundler like webpack? if yes how do you solve the import '../../../../../shared.ts' problem? Or do you use node modules in a monorepo? Compared to other languages I found these questions surprisingly difficult to answer and solutions often quite cumbersome, e.g. if I want to share one small file in my project I don't want to maintain a public npm module for it...
The question is, is it worth it?<p>I'm starting to feel behind the curve and I want to learn new stacks like Next.js, Typescript and GraphQL. Anyone else feeling this way or have already gone through that learning curve?
One critical thing for TypeScript's success that I wish for the Lua community is that it paved a roadmap for typing a huge chunk of the JS ecosystem. Porting to TypeScript can be entirely incremental, and you usually have a wealth of types coming in from dependencies. The UX here is going to be one of the best as far as ports go, as usually porting feels negative value up front
I've never increased my productivity by using Typescript, although I really tried very hard to like it. It just keeps bugging me. It's a constant stream of interruptions that force me to please the TS compiler, compared to having a rare type issue a once in a while in plain JS.<p>Besides that, I've never been a Microsoft fanboy(to say the least) and it's worrying me that almost the entire JS eco system falls in the hands of that company; Github, VSCode, Typescript, NPM, etc.. Am I alone in this?<p>There is so much good stuff in the JS world, but we seem to adhere to a few companies and a few systems more and more. Being a 'Javascript' developer today only has very little to do with Javascript. It's about React, Redux, Hooks, ESLint, Prettier, Typescript, etc.. Oh, and don't forget to do it Agile, another joy and productivity killer. And when you don't agree with this stack you're either not so smart or still need to learn to 'understand' it.