[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.

[root_axis]

You write all your code in TS - great.

You run node with the TS support - great.

That doesn't explain how your front-end TS code is transformed into JS. You seem to be suggesting that node does it automatically, but it doesn't. The explanation of your setup isn't adding up.

[austin-cheney]

> That doesn't explain how your front-end TS code is transformed into JS.

Node will do that at run time. Its automatic. Functions do not have to execute to receive this benefit. They just have to be imported. Ensure you are using a very recent version of Node.

[root_axis]

Yes, but how does your http server deliver the imported code to the front-end? Are you using some type of streaming bundler that does real time builds? Something isn't making sense here.

[austin-cheney]

On application startup I assemble together the various front end files I need and store this in memory as a string. When the server sees a request for the desired page I respond with the desired string.

Since I am not handcuffed by some giant framework I have maximum flexibility to do what makes sense.

[root_axis]

> On application startup I assemble together the various front end files I need and store this in memory as a string.

So in other words, you created your own bundler?

Node isn't actually doing the work for you on the front-end.

[austin-cheney]

Again, I never said Node is did anything for the front end.