In this industry where we are all a little afraid to admit that we don’t know something, it’s nice to be reminded that everyone is always learning all the time and that there’s no way any of us can know everything.
I’m enjoying the learning process, despite its paper cuts, and love where I work. I enjoy TS itself but I do wish the process of setting up a new project/config stuff were more streamlined. Maybe in the future!
Btw, you probably already know this, but if you don’t. The later versions of Node can run typescript natively. By “run”, I mean, it can run a subset of the language, if your project indirectly or indirectly references a file that has “decorators” or something like that, then you’ll need to use another compiler.
ts-node or tsx are runners that I use typically if I just want to “run” something. They’re basically zero config runners and I can debug with them with VS Code.
No worries on the ranting!
In this industry where we are all a little afraid to admit that we don’t know something, it’s nice to be reminded that everyone is always learning all the time and that there’s no way any of us can know everything.
I’m enjoying the learning process, despite its paper cuts, and love where I work. I enjoy TS itself but I do wish the process of setting up a new project/config stuff were more streamlined. Maybe in the future!
Yeah, absolutely agreed.
Btw, you probably already know this, but if you don’t. The later versions of Node can run
typescriptnatively. By “run”, I mean, it can run a subset of the language, if your project indirectly or indirectly references a file that has “decorators” or something like that, then you’ll need to use another compiler.ts-nodeortsxare runners that I use typically if I just want to “run” something. They’re basically zero config runners and I can debug with them with VS Code.Yeah, I’ve read about the development of the ability to run TS natively in Node. It sounds really promising!
I’m not familiar with ts-node though. I’ll have to check that out.