@@mukeshsoni I'm wondering how using `ts-node/register` compares to `@babel/register` + `@babel/preset-typescript` (other than the optional runtime typechecking). Any other thoughts you have on `ts-node` would be greatly appreciated!
@@HarrySolovay Ah, we never tried the `@babel/preset-typescript` option, so can't comment on that. Our node code is written in javascript and client code is written in typescript. We do server rendering and so `require` the client code from the server. Which is where we just dropped in `ts-node` and it worked with a few tweaks for syncing typescript config across client and `ts-node`.
Congratulations with 10K followers! Thank you for your amazing work!
Semi-random question: what're your thoughts on using ts-node in production?
We use ts-node in production in our company. Haven't had any problems yet. What exactly do you want to know?
@@mukeshsoni I'm wondering how using `ts-node/register` compares to `@babel/register` + `@babel/preset-typescript` (other than the optional runtime typechecking). Any other thoughts you have on `ts-node` would be greatly appreciated!
@@HarrySolovay Ah, we never tried the `@babel/preset-typescript` option, so can't comment on that.
Our node code is written in javascript and client code is written in typescript. We do server rendering and so `require` the client code from the server. Which is where we just dropped in `ts-node` and it worked with a few tweaks for syncing typescript config across client and `ts-node`.
@@mukeshsoni Gotcha. Such a cool way of doing things.
Great example. Just saved my project :)