You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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).
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?
Activity
blakeembrey commentedon Apr 27, 2016
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 commentedon Sep 28, 2016
So @blakeembrey, can we now use it in production? As in
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 commentedon Sep 28, 2016
Definitely your choice, go ahead 😄 There's no heavy overheads.
Diluka commentedon Oct 16, 2017
using
ts-node -F .
to run ts code missing metadata.reflect-metadata
can't get field's type.tsc && node .
is OKblakeembrey commentedon Oct 16, 2017
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 commentedon Oct 17, 2017
So, should I use in production?
ts-node .
ortsc && node .
blakeembrey commentedon Oct 17, 2017
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 commentedon Dec 26, 2017
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 commentedon Dec 31, 2017
It's the default behaviour. See https://github.com/TypeStrong/ts-node/releases/tag/v4.0.0.
leotm commentedon Sep 20, 2018
The release note mentions use --type-check for type checking behaviour, but its not mentioned again in the docs?
blakeembrey commentedon Sep 20, 2018
That’s because it was three major releases ago and the behaviour was reverted. It confused other people to not type check by default.
44 remaining items