[austin-cheney]

I write in vanilla TypeScript. I do not have any build step in my application. Since Node now supports native type stripping I don't have a compile step either. I just write my code and then point node at the main file, and this even includes front-end code for the browser.

[thisoneisreal]

Can you explain more about how the front end aspect works? I'm not clear how the front end code could by TypeScript without a build step, unless I'm misreading.

[austin-cheney]

Node strips types on all imported code regardless of where that code executes.

[root_axis]

Node doesn't run in the browser.

[umvi]

Presumably Node is the server (back end), and when the browser requests a TS file, Node is stripping the types before serving it to the browser.

[root_axis]

That presumption is wrong, and doesn't quite make sense if you think about it.

[umvi]

Why doesn't it make sense? I actually do exactly this in my own setup, but with golang instead of Node.

[austin-cheney]

I am aware and it’s not what I said.

[root_axis]

You literally said "this even includes front-end code for the browser".

So what exactly are you referring to here?

[austin-cheney]

I write all my application code in TypeScript, even if it is for the browser. I then import all that code into Node regardless of whether it will execute in Node. All code that will not execute in Node needs to be wrapped in a function for safety, because global references like "document" or "window" will not work in Node.