Should I use it in production?

[aayushkapoor206]

I couldn't find any mention about it in the readme

[blakeembrey]

No, not really. In production you'd want to only be in transpile mode (you should have already type checked). If someone wants to contribute some PRs for this functionality, we can get it in. Otherwise I'd wait for #44.

[prashaantt]

So @blakeembrey, can we now use it in production? As in

$ ts-node -F server.ts

I currently do tsc && node build/server.js, but the very succinctness and beauty of the above is totally worth it if I'll get no significant overheads over the second option.

[blakeembrey]

Definitely your choice, go ahead 😄 There's no heavy overheads.

[Diluka]

using ts-node -F . to run ts code missing metadata. reflect-metadata can't get field's type.

tsc && node . is OK

[blakeembrey]

That make sense to me. Fast mode isn’t using type information, it’s just plain transpiling files on the fly. That’s not equivalent to tsc. Use the regular mode that is if you want type information. It’s a good point though and I can document that.

[Diluka]

So, should I use in production?
ts-node . or tsc && node .

[blakeembrey]

That's not something I can tell you. I can tell you that loading type information has a larger overhead, but it shouldn't impact performance (only memory once started).

[IAMtheIAM]

Hey, FYI there still no documentation mention about the --fast or -F option. I just found it here. That's something worth adding to the readme along with a basic intro about what it does, if its still a valid option. I saw somewhere that it's enabled by default, is that true?

[blakeembrey]

It's the default behaviour. See https://github.com/TypeStrong/ts-node/releases/tag/v4.0.0.

[leotm]

The release note mentions use --type-check for type checking behaviour, but its not mentioned again in the docs?

[blakeembrey]

That’s because it was three major releases ago and the behaviour was reverted. It confused other people to not type check by default.